CVE-2025-22387
Optimizely Configured Commerce ≤ 5.2.2408
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2025-22387 is a high-severity Use of HTTP Request With Sensitive Query String (CWE-598) vulnerability in Optimizely Configured Commerce. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-22387 is a vulnerability discovered in Optimizely Configured Commerce versions before 5.2.2408. The issue arises in requests for resources where the session token is submitted as a URL parameter, exposing information about the authenticated session. This exposure can be leveraged for session hijacking. The vulnerability has a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and is linked to CWE-598.
The vulnerability can be exploited by any unauthenticated attacker with network access, requiring low complexity and no user interaction. By intercepting or accessing the session token embedded in URL parameters—potentially through server logs, proxy logs, or HTTP referer headers—an attacker can hijack an active authenticated session. This grants the attacker the same level of access as the victim, enabling unauthorized actions within the application and potential exposure of sensitive session-bound data.
Optimizely has published a security advisory, COM-2024-06, detailing the issue and mitigation at https://support.optimizely.com/hc/en-us/articles/32695551034893-Configured-Commerce-Security-Advisory-COM-2024-06. Vulnerable installations should upgrade to Optimizely Configured Commerce 5.2.2408 or later, where the issue is addressed.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-2768
Vulnerability Data
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…
more
session hijacking.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.4.5V14.2.1
Mitigating Controls (NIST 800-53 r5) AI
Requiring confidentiality and integrity protection for transmitted data reduces exposure of sensitive query parameters even though the control does not forbid placing secrets in URLs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent embedding sensitive data in query strings as part of input-handling and data-flow design.
HTTPS encryption protects query strings in transit but does not address the root design flaw of placing sensitive data in URLs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect sensitive data leakage via query strings.
DLP solutions can detect and block sensitive data in URLs.
Network security controls can enforce HTTPS and block sensitive data in URLs.
Application security requirements should mandate avoiding sensitive data in query strings.
Secure architecture principles discourage exposing sensitive data in URLs.
Secure coding standards directly prohibit placing secrets in query parameters.