How severe is CVE-2025-22387?

CVE-2025-22387 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2025-22387 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-22387?

CVE-2025-22387 affects Optimizely Configured Commerce. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-22387?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-22387 have an EU (EUVD) identifier?

Yes. CVE-2025-22387 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-2768.

When was CVE-2025-22387 published?

CVE-2025-22387 was published on 2025-01-04 and last updated on 2026-06-17.

CVE-2025-22387

CVE-2025-22387 is a high-severity vulnerability in Optimizely Configured Commerce with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-598.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (29th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-2768
Weakness: CWE-598
Affected product: Optimizely Configured Commerce
Published: 2025-01-04
Last modified: 2026-06-17

Description

An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity issue exists in requests for resources where the session token is submitted as a URL parameter. This exposes information about the authenticated session, which can be leveraged for session hijacking.

Frequently asked questions

What is CVE-2025-22387?: An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity issue exists in requests for resources where the session token is submitted as a URL parameter. This exposes information about the authenticated session, which can be leveraged for session hijacking.
How severe is CVE-2025-22387?: CVE-2025-22387 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-22387 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-22387?: CVE-2025-22387 affects Optimizely Configured Commerce. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-22387?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-22387 have an EU (EUVD) identifier?: Yes. CVE-2025-22387 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-2768.
When was CVE-2025-22387 published?: CVE-2025-22387 was published on 2025-01-04 and last updated on 2026-06-17.

References

https://support.optimizely.com/hc/en-us/articles/32695551034893-Configured-Commerce-Security-Advisory-COM-2024-06

Affected products (1)

cpe:2.3:a:optimizely:configured_commerce:*:*:*:*:*:*:*:*

More vulnerabilities in Optimizely Configured Commerce

CVE-2024-56174 — High (CVSS 8.1): In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed in users'…
CVE-2025-22384 — High (CVSS 7.5): An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity issue concerning business…
CVE-2025-22386 — High (CVSS 7.3): An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity session issue exists in…
CVE-2024-56175 — Medium (CVSS 6.1): In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed in users'…
CVE-2025-22385 — Medium (CVSS 5.9): An issue was discovered in Optimizely Configured Commerce before 5.2.2408. For newly created accounts, the Commerce B2B…
CVE-2024-56173 — Medium (CVSS 4.7): In Optimizely Configured Commerce before 5.2.2408, malicious payloads can be stored and subsequently executed in users'…

All CVEs affecting Optimizely Configured Commerce →

Other CWE-598 vulnerabilities

CVE-2025-69270 — Critical (CVSS 9.8): Information Exposure Through Query Strings in GET Request vulnerability in Broadcom DX NetOps Spectrum on Windows,…
CVE-2023-6014 — Critical (CVSS 9.8): An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.
CVE-2025-56551 — High (CVSS 8.2): An issue in DirectAdmin v1.680 allows unauthorized attackers to manipulate the page layout and replace the legitimate…
CVE-2021-21594 — High (CVSS 8.2): Dell PowerScale OneFS versions 8.2.2 - 9.1.0.x contain a use of get request method with sensitive query strings…
CVE-2026-23846 — High (CVSS 8.1): Tugtainer is a self-hosted app for automating updates of Docker containers. In versions prior to 1.16.1, the password…
CVE-2019-6531 — High (CVSS 8.1): An attacker could retrieve passwords from a HTTP GET request from the Kunbus PR100088 Modbus gateway versions prior to…

Browse all CWE-598 vulnerabilities →