CVE-2024-56175: Optimizely Configured Commerce · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium · fixed in 5.2.2408 : update Optimizely Configured Commerce when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- Optimizely Configured Commerce before 5.2.2408
- Patch
- Available – fixed in 5.2.2408
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
In the interim, implement strict input validation and sanitization on all user-supplied data, especially list item names, to prevent injection of malicious scripts. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Regularly audit client-side templates and rendering logic to ensure no unsafe dynamic content injection occurs. Monitor application logs and user reports for suspicious activity indicative of attempted XSS exploitation. Educate developers on secure coding practices related to client-side templating and XSS prevention. Additionally, consider deploying web application firewalls (WAFs) with rules targeting XSS payloads to provide an additional layer of defense.
Description
In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed in users' browsers under specific conditions: XSS from client-side template injection in list item names.