# CVE-2025-22386: Security feature bypass in n/a

> Attackers can reuse session tokens from logged-out users to maintain unauthorized access to the B2B storefront.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Jan 2025
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-jcgv-xjw5-6wp4

## What is CVE-2025-22386?

CVE-2025-22386 is a high-severity vulnerability in n/a, published on 4 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2025-22386?

It affects 1 product.


Products: Optimizely Configured Commerce.

## How do I fix CVE-2025-22386?

No fix has been published for CVE-2025-22386 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-22386 being exploited?

There is no known exploitation of CVE-2025-22386 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-56174](https://insights.sbomify.com/CVE-2024-56174/): Cross-site scripting in n/a (high 8.1)
- [CVE-2025-22384](https://insights.sbomify.com/CVE-2025-22384/): Business logic in n/a (high 7.5)
- [CVE-2025-22387](https://insights.sbomify.com/CVE-2025-22387/): Information disclosure in n/a (high 7.5)
- [CVE-2024-56175](https://insights.sbomify.com/CVE-2024-56175/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-22385](https://insights.sbomify.com/CVE-2025-22385/): Missing authorization in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22386 and fix it if it is affected.

What it is: CVE-2025-22386 is a high-severity vulnerability in n/a, published on 4 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-22386 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22386/ (Markdown: https://insights.sbomify.com/CVE-2025-22386/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22386
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22386
- OSV: https://osv.dev/vulnerability/CVE-2025-22386

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22386/
Summaries are generated and may contain mistakes; the official description above is the record.