CVE-2024-56173

4.7 MEDIUM

📋 TL;DR

This is a stored cross-site scripting (XSS) vulnerability in Optimizely Configured Commerce where malicious JavaScript in SVG documents can be injected and later executed in users' browsers. It affects all users of vulnerable Configured Commerce instances, potentially allowing attackers to steal session cookies, redirect users, or perform actions on their behalf.

💻 Affected Systems

Products:
  • Optimizely Configured Commerce
Versions: All versions before 5.2.2408
Operating Systems: All platforms running Configured Commerce
Default Config Vulnerable: ⚠️ Yes
Notes: Requires SVG upload or injection capability; affects both authenticated and unauthenticated users depending on configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, take over admin accounts, manipulate e-commerce transactions, or deploy malware to customer browsers.

🟠

Likely Case

Attackers inject malicious scripts that steal user session data, redirect to phishing sites, or deface the e-commerce interface.

🟢

If Mitigated

With proper input validation and output encoding, the attack would fail to execute, limiting impact to attempted exploitation logs.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

XSS vulnerabilities are commonly exploited; SVG-based XSS requires specific injection points but is well-documented.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 5.2.2408 or later

Vendor Advisory: https://support.optimizely.com/hc/en-us/articles/32344323720973-Configured-Commerce-Security-Advisory-COM-2024-01

Restart Required: Yes

Instructions:

1. Backup your Configured Commerce instance. 2. Apply the official patch from Optimizely. 3. Restart the application server. 4. Verify the fix by testing SVG upload functionality.

🔧 Temporary Workarounds

Disable SVG uploads

all

Temporarily block SVG file uploads through web application firewall or configuration changes.

Configure WAF to block Content-Type: image/svg+xml uploads
Modify application to reject SVG file extensions

Implement Content Security Policy

all

Add CSP headers to restrict script execution from untrusted sources.

Add header: Content-Security-Policy: script-src 'self'

🧯 If You Can't Patch

  • Implement strict input validation for all user-supplied SVG content
  • Deploy a web application firewall with XSS protection rules

🔍 How to Verify

Check if Vulnerable:

Test by uploading an SVG file containing JavaScript payload and checking if it executes when rendered.

Check Version:

Check Configured Commerce admin panel or application properties for version number.

Verify Fix Applied:

After patching, attempt the same SVG XSS test; execution should be prevented.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SVG file uploads
  • JavaScript errors from SVG rendering
  • Multiple failed SVG upload attempts

Network Indicators:

  • HTTP requests with SVG content containing script tags
  • Unusual outbound connections after SVG rendering

SIEM Query:

source="web_server" AND (uri_path="*.svg" OR content_type="image/svg+xml") AND (body="<script>" OR body="javascript:")

🔗 References

📤 Share & Export