CVE-2025-22384
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA business logic vulnerability in Optimizely Configured Commerce allows attackers to purchase discontinued products by intercepting and manipulating HTTP requests before they reach the server. The application appears to rely on client-side validation or lacks proper server-side enforcement to prevent purchasing of products marked as discontinued.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.2.2408CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Optimizely Configured Commerce versionLocate the version file or assembly info within the Commerce deployment directory, typically found in the application binaries or version configuration fileAffected if The installed version is below 5.2.2408 (e.g., 5.2.2300, 5.1.x, etc.)
-
Verify product discontinuation status storageQuery the product database or inspect the product management module to confirm how discontinued products are marked in the systemAffected if Products have a discontinued flag or status field that exists in the database
-
Test purchase flow with discontinued productAdd a discontinued product to cart via normal UI, then intercept the checkout HTTP request using a proxy tool and attempt to submit the orderAffected if The order completes successfully despite the product being marked as discontinued in the backend
-
Inspect server-side order validation logicReview the order processing code or API endpoint responsible for completing purchases to determine if product status is checked server-side before order finalizationAffected if No server-side code validates product availability status from the database during checkout, or validation relies solely on client-submitted parameters
-
Check for API endpoints accepting product purchase requestsReview the commerce API endpoints that handle add-to-cart and checkout operations to see if they accept and process product IDs without re-validating product statusAffected if API endpoints accept product IDs and process orders without querying the current product status from the database
You are affected if your Optimizely Configured Commerce version is below 5.2.2408 and the system allows purchasing discontinued products without server-side validation of product status.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.2.2408
Implement robust server-side validation to verify product availability status directly from the database before completing any purchase, regardless of client-submitted request parameters.
5.2.2408 or later
- 1. Identify the current version of Optimizely Configured Commerce by checking the application or admin panel
- 2. Schedule a maintenance window for the upgrade
- 3. Back up the current database and application files
- 4. Upgrade the Configured Commerce instance to version 5.2.2408 or later (preferably the latest stable release)
- 5. After upgrade, verify the fix by testing that discontinued products cannot be added to cart via altered requests
- 6. Monitor the application logs for any post-upgrade issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22384 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data