# CVE-2026-96600: Isotope eCommerce through 2.9.10 SQL Injection via Backend Callbacks

> Authenticated backend users can exploit blind SQL injection in Isotope eCommerce callbacks to extract arbitrary database contents, including password hashes.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-7pjx-8r2g-hwpp

## What is CVE-2026-96600?

CVE-2026-96600 is a high-severity SQL injection vulnerability in isotope-core, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Isotope eCommerce through 2.9.10 contains a blind SQL injection vulnerability in backend callbacks that interpolate request-controlled identifiers and administrator-supplied values directly into SQL statements. Authenticated Contao backend users with Isotope module permissions can exploit conditional and time-based injection payloads to extract arbitrary database contents including user password hashes from the tl_user table.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-96600 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96600 is a high-severity SQL injection vulnerability in isotope-core, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96600 in the wild and no public exploit code.

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-96600/ (Markdown: https://insights.sbomify.com/CVE-2026-96600/index.md)
```

## Sources

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

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