CVE-2024-56173VulnerabilityPublished 18 Dec 2024

CVE-2024-56173: n/a

Source CVE Database V5

Not known to be exploited · CVSS 4.7 Medium · fixed in 5.2.2408 : update Optimizely Configured Commerce when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% 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:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-56173, organizations should prioritize upgrading Optimizely Configured Commerce to version 5.2.2408 or later once an official patch is released. In the interim, implement strict input validation and sanitization on all SVG content uploaded or rendered by the platform, specifically filtering out or encoding JavaScript within SVG files. Employ Content Security Policy (CSP) headers to restrict the execution of inline scripts and limit the sources from which scripts can be loaded, reducing the risk of XSS exploitation. Regularly audit and monitor web application logs for unusual activity or injection attempts involving SVG files. Educate developers and administrators on secure handling of SVG and other vector graphics formats, emphasizing the risks of embedded scripts. Consider disabling or restricting SVG uploads if feasible until a patch is applied. Additionally, implement multi-factor authentication and session management best practices to reduce the impact of potential session hijacking. Conduct penetration testing focused on XSS vectors involving SVG content to identify residual risks. Finally, maintain up-to-date threat intelligence feeds to detect emerging exploits targeting this vulnerability.

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 JavaScript in an SVG document.

Impact

The primary impact of CVE-2024-56173 is the potential for attackers to execute malicious JavaScript in the browsers of users interacting with vulnerable Optimizely Configured Commerce platforms. This can lead to partial confidentiality breaches, such as theft of session tokens, user data exposure, or unauthorized actions performed in the context of the victim's session. Although the vulnerability does not directly affect data integrity or system availability, the confidentiality compromise can facilitate further attacks like session hijacking or phishing. The requirement for user interaction limits the attack's reach but does not eliminate risk, especially in e-commerce environments where users frequently interact with dynamic content. Organizations relying on Optimizely Configured Commerce for online storefronts or customer engagement may face reputational damage, loss of customer trust, and potential regulatory consequences if user data is compromised. The absence of known exploits in the wild provides a window for proactive mitigation, but the vulnerability's presence in widely used e-commerce software means the attack surface is significant. The scope change indicates that the vulnerability could affect multiple components or users beyond the initially targeted resource, increasing potential impact.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.optimizely.com/hc/en-us/articles/32344323720973-Configured-Commerce-Security-Advisory-COM-2024-01 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 02:12 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats