CVE-2024-56174: In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed

Q: How do I fix CVE-2024-56174?

configured commerce: upgrade to 5.2.2408. Exact commands for each OS are on this page.

Q: Is CVE-2024-56174 being exploited?

CVE-2024-56174 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-56174 affect?

CVE-2024-56174 affects configured commerce. Severity is high (CVSS 8.1). 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.

Q: How urgent is CVE-2024-56174?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.1REMOTEUPGRADE

CVE-2024-56174 is a high-severity flaw (CVSS 8.1) affecting configured commerce. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 68%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-12-18
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: optimizely

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-12-18 06:15 UTCPublished CVE record published
2026-06-17 08:11 UTCUpdated Record last modified

optimizely configured commerce UPGRADE

Affected: < 5.2.2408

Fixed in: 5.2.2408

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy configured-commerce || rpm -q configured-commerce || configured-commerce --version

2. UPGRADE to 5.2.2408 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade configured-commerce

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade configured-commerce

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-56174?

configured commerce: upgrade to 5.2.2408. Exact commands for each OS are on this page.

Is CVE-2024-56174 being exploited?

CVE-2024-56174 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-56174 affect?

CVE-2024-56174 affects configured commerce. Severity is high (CVSS 8.1). 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.

How urgent is CVE-2024-56174?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-22387 HIGH 7.5 UPGRADE An issue was discovered in Optimizely Configured Commerce before 5.2.2408
CVE-2025-22386 HIGH 7.3 UPGRADE An issue was discovered in Optimizely Configured Commerce before 5.2.2408
CVE-2025-22385 MEDIUM 5.9 UPGRADE An issue was discovered in Optimizely Configured Commerce before 5.2.2408
CVE-2025-22384 HIGH 7.5 UPGRADE An issue was discovered in Optimizely Configured Commerce before 5.2.2408
CVE-2025-22383 MEDIUM 4.6 UPGRADE An issue was discovered in Optimizely Configured Commerce before 5.2.2408

References

← Back to latest CVEs