VulnerabilityPublished 4 Jan 2025Updated 6 Jan 2025

CVE-2025-22387: Optimizely Configured Commerce · Use of HTTP Request With Sensitive Query String

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 5.2.2408 : patch Optimizely Configured Commerce soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects: Optimizely Configured Commerce before 5.2.2408
Patch: Available – fixed in 5.2.2408

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Upgrade Optimizely Configured Commerce to version 5.2.2408 or later where this vulnerability is addressed.
Immediately audit all web application code and configurations to ensure session tokens or other sensitive authentication data are never included in URL query parameters.
Implement secure session management practices by using HTTP-only, Secure, and SameSite cookies to store session tokens instead of URL parameters.
Review and sanitize web server and proxy logs to remove any stored session tokens that may have been logged.
Enforce HTTPS across all communications to prevent interception of tokens in transit.
Educate developers and security teams about the risks of sensitive data in URLs and promote secure coding standards.
Monitor network traffic and logs for unusual access patterns that may indicate session hijacking attempts.
Consider implementing additional session security controls such as IP binding, user-agent validation, and short session expiration times to reduce the window of exploitation.
Conduct penetration testing and vulnerability assessments focused on session management to detect similar issues proactively.

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.

Impact

The primary impact of this vulnerability is the compromise of confidentiality through session hijacking. Attackers who obtain the session token can impersonate legitimate users, potentially gaining unauthorized access to sensitive business data, customer information, or administrative functions within Optimizely Configured Commerce platforms. This can lead to data breaches, fraud, and loss of customer trust. Since the vulnerability does not affect integrity or availability directly, the main risk is unauthorized data access. The ease of exploitation (no authentication or user interaction required) and the wide network attack vector increase the likelihood of exploitation once discovered. Organizations relying on affected versions face increased risk of account takeover and subsequent downstream attacks. The exposure of session tokens in URLs also increases the risk from insider threats or compromised network infrastructure. Given Optimizely's use in e-commerce and digital experience management, the impact on business operations and reputation can be significant.

Summary

CVE-2025-22387 is a vulnerability classified under CWE-598, which concerns the use of HTTP GET request methods with sensitive query strings. Specifically, in Optimizely Configured Commerce versions prior to 5.2.2408, session tokens are transmitted as URL parameters in GET requests. This insecure design flaw leads to exposure of authenticated session tokens in URLs, which can be logged in browser history, web server logs, proxy logs, or intercepted by network sniffers. Because session tokens are critical for maintaining authenticated user sessions, their exposure allows attackers to hijack active sessions without needing credentials or user interaction. The vulnerability is remotely exploitable over the network without privileges or authentication, increasing its risk profile. The CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates high confidentiality impact with no impact on integrity or availability. No patches or exploits are currently documented, but the issue is publicly known since January 2025. The root cause is the insecure practice of embedding sensitive tokens in URLs rather than using secure HTTP headers or cookies. This vulnerability highlights the importance of secure session management and avoiding sensitive data in URLs.

CWE-598Use of HTTP Request With Sensitive Query String (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.
Implementation
When sending sensitive information, only include it in the request body or request headers instead of the query string. This may require avoiding use of GET requests.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V3.1.1 (opens in a new tab)
V13.1.3 (opens in a new tab)
V8.3.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.optimizely.com/hc/en-us/articles/32695551034893-Configured-Commerce-Security-Advisory-COM-2024-06 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 25 Feb 2026, 22:12 UTC

WeaknessesCWE-598

Technical details

References

Community reviews

Related threats