# CVE-2026-96599: Isotope eCommerce through 2.9.10 Weak Order Identifier Generation

> Attackers can guess order identifiers to access sensitive customer data and purchased files due to weak random number generation.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-fvwm-j9pj-rw38

## What is CVE-2026-96599?

CVE-2026-96599 is a high-severity vulnerability in isotope-core, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Isotope eCommerce through 2.9.10 derives order identifiers from uniqid() instead of a cryptographically secure source, allowing unauthenticated attackers to guess identifiers. Guest orders lack ownership verification, enabling attackers to access order details including billing address, customer information, and purchased files by supplying a guessed uid parameter.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2026-96599?


## How do I fix CVE-2026-96599?

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

## Is CVE-2026-96599 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-96599 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96599 and fix it if it is affected.

What it is: CVE-2026-96599 is a high-severity vulnerability in isotope-core, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-96599 exists.

Affected product: isotope-core. 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-2026-96599/ (Markdown: https://insights.sbomify.com/CVE-2026-96599/index.md)
```

## Sources

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

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