CVE-2024-56174: Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 8.1 High · fixed in 5.2.2408 : patch Optimizely Configured Commerce soon.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% 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:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation 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
1. 2. If you cannot patch yet, implement strict input validation and sanitization on all user-supplied data, especially within the search history feature, to prevent injection of malicious scripts. 3. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4. Use HTTP-only and secure cookies to protect session tokens from theft via XSS. 5. Conduct thorough code reviews and security testing focusing on client-side template rendering and user input handling. 6. Monitor web application logs and user activity for signs of suspicious behavior indicative of exploitation attempts. 7. Educate development teams on secure coding practices related to template injection and XSS prevention. 8. Consider implementing web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting the affected functionality.
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 search history.