CVE-2025-22384VulnerabilityPublished 4 Jan 2025Updated 6 Jan 2025

CVE-2025-22384: External Control of Assumed-Immutable Web Parameter

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, 06:26 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% 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 2026-10-26.

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 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

In the interim, implement strict server-side validation of all web parameters related to product availability and purchasing workflows to ensure that discontinued products cannot be ordered regardless of client-side input. Employ input validation and parameter integrity checks using cryptographic methods such as signed tokens or HMACs to prevent tampering of assumed-immutable parameters. Monitor transaction logs for unusual purchase patterns involving discontinued products and establish alerting mechanisms for suspicious activity. Restrict API endpoints and storefront request handling to reject requests with invalid or manipulated parameters. Conduct thorough code reviews and business logic testing to identify and remediate similar weaknesses. Additionally, consider implementing rate limiting and anomaly detection to reduce the risk of automated exploitation attempts. Educate development and security teams about the risks of external control over immutable parameters to prevent recurrence in future releases.

Description

An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity issue concerning business logic exists in the Commerce B2B application, which allows storefront visitors to purchase discontinued products in specific scenarios where requests are altered before reaching the server.

Impact

The primary impact of CVE-2025-22384 is the unauthorized purchase of discontinued products, which can lead to direct financial losses for merchants and confusion in inventory management. Attackers exploiting this vulnerability can bypass business rules designed to prevent sales of obsolete or unavailable items, potentially resulting in revenue leakage and increased operational overhead to resolve fraudulent or invalid orders. Additionally, the exposure of business logic flaws may aid attackers in crafting further attacks or exploiting other weaknesses in the commerce platform. While the vulnerability does not compromise system integrity or availability, the confidentiality impact is significant as it reveals internal product lifecycle controls and transactional processes. For organizations worldwide, especially those with large-scale e-commerce operations using Optimizely Configured Commerce, this vulnerability could undermine customer trust and damage brand reputation. The absence of required authentication and user interaction lowers the barrier to exploitation, increasing the risk of automated or large-scale abuse. Although no known exploits exist currently, the potential for future exploitation necessitates proactive mitigation to avoid financial and reputational harm.

Summary

CVE-2025-22384 identifies a business logic vulnerability in Optimizely Configured Commerce prior to version 5.2.2408. The issue is categorized under CWE-472, which involves external control of an assumed-immutable web parameter. In this case, the vulnerability allows attackers—without authentication or user interaction—to manipulate HTTP requests to the storefront application, enabling the purchase of products that have been discontinued and should no longer be available for sale. The root cause lies in the application’s failure to properly validate or enforce immutability on certain web parameters that control product availability status. This flaw can be exploited remotely over the network (AV:N) with low attack complexity (AC:L), and no privileges or user interaction are required (PR:N, UI:N). The vulnerability impacts confidentiality by potentially exposing business logic and transactional data related to discontinued products, but does not affect integrity or availability. Although no public exploits have been reported, the vulnerability’s CVSS 3.1 base score is 7.5, reflecting its high severity. The lack of patch links suggests that a fix may be pending or not publicly disclosed at the time of reporting. Organizations relying on Optimizely Configured Commerce for B2B storefronts should be aware of this issue as it could lead to unauthorized transactions, financial losses, and erosion of customer trust. The vulnerability highlights the importance of robust parameter validation and business logic enforcement in e-commerce platforms.

CWE-472External Control of Assumed-Immutable Web Parameter (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
XML Schema Poisoning (opens in a new tab)
Session Credential Falsification through Manipulation (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

WeaknessesCWE-472

Technical details

References

Community reviews

Related threats