dbcve.org
Configured CommerceApplication · Optimizely

CVE-2025-22387

HIGH · 7.5 CVSS v3.1 Published 2025-01-04
Fix available
A fix is available. Upgrade to 5.2.2408 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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

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

Optimizely Configured Commerce before version 5.2.2408 transmits session tokens as URL parameters instead of using secure methods like HTTP-only cookies or headers. This exposes session credentials in server logs, browser history, proxy logs, and HTTP referrer headers, enabling attackers to hijack authenticated user sessions.

MitigationMigrate session token handling from URL parameters to secure HTTP-only cookie-based or header-based authentication. Update all affected endpoints and invalidate potentially compromised sessions.

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

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

  1. Identify the installed Optimizely Configured Commerce version
    Locate the version information in the application admin panel, assembly metadata, or deployment documentation, and compare it to the affected range of versions before 5.2.2408
    Affected if The installed version is any version before 5.2.2408
  2. Examine server access logs for session tokens in URLs
    Search web server logs (IIS, Apache, or nginx) for request patterns where URLs contain token, sessionid, or similar parameter names with alphanumeric values
    Affected if Session identifiers appear as URL query parameters in server logs
  3. Capture and inspect HTTP traffic
    Use browser developer tools or a proxy to observe outgoing requests during authentication and subsequent navigation, noting whether session credentials appear in the URL rather than headers or cookies
    Affected if Session tokens are transmitted as URL query parameters instead of HTTP headers or cookies
  4. Review browser history and proxy logs
    Check browser history files or corporate proxy logs for cached URLs containing session-related parameter values
    Affected if Browser history or proxy logs contain URLs with visible session token values
  5. Inspect application session configuration
    Examine the application's configuration files or admin settings related to authentication and session management, looking for any settings that specify URL-based token transmission
    Affected if Configuration explicitly allows or requires session tokens to be passed via URL parameters

You are affected if your Optimizely Configured Commerce version is before 5.2.2408 AND you observe session tokens being transmitted as URL parameters in any log or network traffic.

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

Migrate session token handling from URL parameters to secure HTTP-only cookie-based or header-based authentication. Update all affected endpoints and invalidate potentially compromised sessions.

Recommended fix High confidence

5.2.2408

  1. Back up your current Optimizely Configured Commerce installation and database
  2. Upgrade to version 5.2.2408 or later
  3. After upgrade, verify that session tokens are no longer transmitted as URL parameters (should use cookies or headers instead)
  4. Test authentication flows to confirm sessions work correctly post-upgrade

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

Fix this in Configured Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22387 — 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-22387 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