CVE-2025-22386: An issue was discovered in Optimizely Configured Commerce before 5.2.2408

Q: How do I fix CVE-2025-22386?

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

Q: Is CVE-2025-22386 being exploited?

CVE-2025-22386 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-2025-22386 affect?

CVE-2025-22386 affects configured commerce. Severity is high (CVSS 7.3). An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity session issue exists in the Commerce B2B application, affecting the longevity of active sessions in the storefront. This allows session tokens tied

Routine

HIGH 7.3UPGRADE

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

An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity session issue exists in the Commerce B2B application, affecting the longevity of active sessions in the storefront. This allows session tokens tied to logged-out sessions to still be active and usable.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-613
Published	2025-01-04
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

2025-01-04 02:15 UTCPublished CVE record published
2026-06-17 08:46 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-2025-22386?

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

Is CVE-2025-22386 being exploited?

CVE-2025-22386 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-2025-22386 affect?

CVE-2025-22386 affects configured commerce. Severity is high (CVSS 7.3). An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity session issue exists in the Commerce B2B application, affecting the longevity of active sessions in the storefront. This allows session tokens tied

How urgent is CVE-2025-22386?

Priority 31/100. High severity

Related CVEs

CVE-2025-22387 HIGH 7.5 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
CVE-2024-56175 MEDIUM 6.1 UPGRADE In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed

References

← Back to latest CVEs