New research: The State of SaaS, October 2026. Read the report

← All storiesSecurity

Optimizely Reports Web Experimentation Security Incident

By Christine James, Editor · November 22, 2026

Optimizely has disclosed a security incident in Web Experimentation that let an unauthorized third party impersonate users and insert malicious JavaScript into customer projects. In its notice dated November 19, 2026, the company says less than 5% of its customers were affected. It says no other Optimizely product was affected.

What Happened

According to Optimizely’s security advisory, the third party exploited a flaw in the Web Experimentation account signup flow. That flaw allowed them to impersonate users on targeted customer accounts. They then used that access to put malicious JavaScript into those customers’ projects.

Optimizely says this was not a credentials breach. The notice describes misuse of the signup flow, rather than stolen credentials, as the way the third party gained access. Its statement that credentials were not breached is separate from its confirmation that customer projects were changed.

The company limits the incident to Web Experimentation. Its broader platform includes content management, experimentation and commerce, but the notice does not extend the incident to those other products.

What Optimizely Changed

Optimizely says it detected the incident, blocked delivery of the malicious code and closed the flaw within three hours of detection. That timing is the company’s stated response window, not a statement about when the incident first began.

The company also says it removed the injected code from all affected projects. According to the notice, no malicious code remains in its systems. Blocking delivery, closing the signup flaw and removing the injected code are the separate actions described in the advisory.

For related vendor notices, HissingKitty maintains a software security incident tracker. The Optimizely account here is limited to what the company says in its notice.

What Customers Should Do Now

Optimizely says it has contacted every Web Experimentation customer directly to confirm whether they were affected. Those direct messages provide the company’s account-specific confirmation, while the public notice describes the incident as a whole.

For customers who do not use Web Experimentation, the company says no action is needed. That instruction is tied to the product a customer uses, not simply whether they buy from Optimizely.

HissingKitty’s Optimizely page collects buyer reviews and shared pricing information separately from this security notice.

Review Optimizely or share what you pay.

Update: Separate Configured Commerce Incident

Optimizely also reported a second, unrelated incident. An unauthorized party accessed a retiring build and deployment server for Configured Commerce between November 10 and November 12, according to its incident update. Optimizely says an injected script was removed from two sites, the server has been shut down permanently, and a forensic review with outside experts is ongoing. Configured Commerce customers should ask Optimizely for written confirmation of whether their instance was affected.

Sources

Optimizely logo

Optimizely on HissingKitty

No bills yet

What teams pay

No ratings yet

Ratings

6

Alternatives listed

See all Optimizely alternatives →

Built Something Like This?

List it free, or tell other teams what you pay today.

More Stories