How Kameleoon secures its JavaScript on your website

Following the November 16 security incident affecting Optimizely Web Experimentation, Kameleoon customers may have questions about the JavaScript that runs on their websites.
We asked Louis Trilles, Kameleoon’s Chief Security Officer, what the incident means for Kameleoon customers, what protections are in place today, and what their own teams can do.
Does the vulnerability reported by Optimizely also affect Kameleoon?
Louis Trilles. Based on our assessment to date, we’ve found no indication that the incident affected Kameleoon or its customers.
In its initial report, Optimizely said an unauthorized party exploited a vulnerability in its Web Experimentation sign-up process and inserted malicious JavaScript into some customer projects. Visitors’ browsers then loaded the malicious code through the affected scripts. Optimizely says it fixed the vulnerability and removed the injected code on November 16.
Who can change Kameleoon’s JavaScript, and how can I see what changed?
Louis Trilles. We use multi-factor authentication and single sign-on to protect access to Kameleoon. We restrict our staff’s access to customer accounts and keep a record of each access.
Your team can see the history of changes to its custom JavaScript in Kameleoon. We continuously monitor the code we serve. Every change triggers an alert. We also run static and dynamic security tests on the platform to look for vulnerabilities.
What are you adding to catch suspicious changes before they go live?
Louis Trilles. We’re developing an AI-assisted security check for changes to the JavaScript we serve. For example, it can flag a change that attempts to send data to an unrecognized external domain. If the check flags a change, we’ll hold it for review before it can go live.
This additional security measure is currently being released.
Is there anything my security team should do?
Louis Trilles. If your site loads third-party scripts, we recommend reviewing your Content Security Policy (CSP). A CSP can limit which scripts a browser runs and which addresses those scripts can send certain requests to. That gives your team a way to reduce the potential impact of a problem with a third-party script. developer.mozilla.org
If your team has questions about its Kameleoon setup or would like help reviewing its CSP, you can reach us directly at [email protected].







