# CVE-2026-72599: e107 e107 - SQL Injection

> Unauthenticated attackers can execute arbitrary SQL via the news item page ID parameter, allowing them to read, modify, or delete all database contents including administrator credentials.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-85cw-qx9x-rj5j

## What is CVE-2026-72599?

CVE-2026-72599 is a critical SQL injection vulnerability in e107, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An SQL injection vulnerability in e107 2.4.0 allows unauthenticated remote attackers to execute arbitrary SQL via the news item page ID parameter. The parameter is concatenated without escaping into a SQL WHERE clause. An unauthenticated attacker can read, modify, or delete all database contents including administrator credentials.

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

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


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

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

## Is CVE-2026-72599 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72599 is a critical SQL injection vulnerability in e107, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72599 in the wild and no public exploit code.

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

## Sources

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

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