Optimizely: Web Experimentation Security Incident
Affected components: Snippet DeliveryWeb Experimentation - Snippet Delivery
Discussed on Hacker News
- 190 points · 2 comments · posted · posted 3 h 54 min before the vendor’s first update
Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.
Timeline of updates
- monitoring
Earlier today, Optimizely identified a security incident in which an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects. We've fixed the vulnerability and removed the injected code from affected projects. We've also taken steps to secure affected user accounts and put additional protections in place to prevent unauthorized code from being delivered.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.optimizely.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Optimizely, started 2026-11-17 01:02 UTC, not resolved, 1 update(s).
- Title
- Web Experimentation Security Incident
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/ftw0fh9wx43z
Optimizely profileRecent Optimizely incidentsAll outages on November 17, 2026Optimizely in November 2026MarkdownJSON