CVE-2024-56175
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStored XSS vulnerability in Optimizely Configured Commerce allows attackers to inject malicious payloads into list item names. The payload is rendered via client-side template injection and executes in victim users' browsers when they view the affected list.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.2.2408CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Optimizely Configured Commerce versionAccess the admin panel or check the application runtime configuration. Typically found under Admin > System > Installation Info, or by inspecting the deployed assemblies/version manifest. Alternatively, check the deployed build version from the application binaries or configuration files.Affected if The installed version is below 5.2.2408 (e.g., 5.2.x, 5.1.x, earlier versions)
-
Confirm list management feature is in useNavigate to the admin interface and verify if the List Manager module is enabled. Check if any custom or out-of-the-box lists exist (e.g., price lists, inventory lists, category lists) by accessing the Lists section in the CMS or Commerce admin dashboard.Affected if The List Manager feature is active and lists are defined in the system
-
Inspect list item name fields for suspicious contentAccess the database directly or export list items via the admin API/interface. Query the list item name fields for patterns typical of XSS payloads such as <script>, <img onerror=, javascript:, alert(, or encoded variants. Use SQL: SELECT * FROM ListItem WHERE Name LIKE '%<%' or similar patterns.Affected if Any list item names contain HTML tags, JavaScript event handlers, or encoded script fragments
-
Review browser console for template injection errorsAs an admin user, navigate to the Lists section in the frontend or admin panel. Open browser developer tools (F12) and check the Console and Network tabs for any client-side template errors, unusual script executions, or requests containing injected payloads.Affected if Console displays unexpected script errors or injected code executes when viewing list items
You are affected if running Optimizely Configured Commerce below version 5.2.2408 AND the List Manager feature is in use, with list item names containing malicious script payloads.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.2.2408
Upgrade to Optimizely Configured Commerce 5.2.2408 or later. Until patched, implement output encoding/sanitization on all list item name fields before rendering.
5.2.2408
- 1. Create a full backup of the current Configured Commerce environment including database and application files
- 2. Review the official release notes for version 5.2.2408 at support.optimizely.com for any specific upgrade instructions
- 3. Schedule a maintenance window for the upgrade process
- 4. Apply the upgrade to Configured Commerce version 5.2.2408 or later following standard upgrade procedures
- 5. Verify the upgrade was successful by checking the application version
- 6. Test that list item names with special characters render safely without executing scripts
- 7. Clear any cached data and restart application services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56175 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-56175 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data