dbcve.org
Configured CommerceApplication · Optimizely

CVE-2025-22386

HIGH · 7.3 CVSS v3.1 Published 2025-01-04
Fix available
A fix is available. Upgrade to 5.2.2408 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable

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 · unedited
An issue was discovered in Optimizely Configured Commerce before 5.2.2408. A medium-severity session issue exists in the Commerce B2B application, affecting the longevity of active sessions in the storefront. This allows session tokens tied to logged-out sessions to still be active and usable.

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 confidence

Session management vulnerability in Optimizely Configured Commerce B2B application where session tokens remain valid and usable after user logout, allowing replay of previously authenticated sessions.

MitigationImplement proper server-side session invalidation upon logout to ensure session tokens are revoked and cannot be reused after termination.

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
Configured CommerceApplication
Affected:< 5.2.2408

CVSS 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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Optimizely Configured Commerce version
    Locate the version information for your Optimizely Configured Commerce installation, typically found in the application admin panel under system settings, or check the assembly/dll version if you have access to the deployment files
    Affected if The installed version is lower than 5.2.2408 (e.g., 5.2.2300, 5.1.x, etc.)
  2. Verify session token configuration
    Access the session management or security configuration settings in the Optimizely admin panel or configuration files to examine how session tokens are generated and handled
    Affected if Session tokens are configured without server-side invalidation on logout or have extended expiration times
  3. Test session invalidation behavior
    Log into the application, capture the session token, perform logout, then attempt to use the original session token in a new request to see if it remains valid
    Affected if The original session token continues to work after logout, indicating sessions are not being invalidated server-side
  4. Review session storage mechanism
    Check where session data is stored (database, distributed cache, etc.) and whether session records are removed or marked invalid upon logout
    Affected if Session records persist in storage after user logout or are not marked as invalidated

Your environment is affected if you are running Optimizely Configured Commerce version below 5.2.2408 AND sessions remain usable after logout, indicating the session replay vulnerability is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.2.2408 or later
Fixed in 5.2.2408
Interim mitigation

Implement proper server-side session invalidation upon logout to ensure session tokens are revoked and cannot be reused after termination.

Recommended fix High confidence

Upgrade to Configured Commerce version 5.2.2408 or later

  1. 1. Identify the current version of Optimizely Configured Commerce currently deployed in your environment
  2. 2. Review the release notes for version 5.2.2408 at support.optimizely.com to understand changes and any prerequisites
  3. 3. Perform a full backup of the database and application files before upgrading
  4. 4. Test the upgrade in a staging or development environment first to verify functionality
  5. 5. Upgrade the Configured Commerce installation to version 5.2.2408 or later
  6. 6. Verify that session tokens are properly invalidated upon logout by testing the logout functionality
  7. 7. Deploy the validated upgrade to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Configured Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22386 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22386 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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