# CVE-2026-8726: SQL Injection in extension "News system" (news)

> Unauthenticated attackers can inject SQL via URL parameters in the TYPO3 News extension's Date Menu plugin if specific settings are not enabled.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** Yes
- **Published:** 19 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-g868-j3qm-4j28

## What is CVE-2026-8726?

CVE-2026-8726 is a high-severity SQL injection vulnerability in TYPO3 Extension "News system", published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The extension fails to properly sanitize user input before using it in a database query. As a result, an unauthenticated attacker can inject arbitrary SQL through a URL parameter on pages using the "Date Menu of news articles" plugin. Exploitation requires the "Date Menu of news articles" plugin to be in use and the TypoScript/Plugin setting disableOverrideDemand not to be enabled.

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

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

10 open source packages ship an affected version, including georgringer/news.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `georgringer/news` | Packagist | All versions | 10.0.4 |
| `georgringer/news` | Packagist | All versions | 10.0.4 |
| `georgringer/news` | Packagist | From 11.0.0 | 11.4.4 |
| `georgringer/news` | Packagist | From 11.0.0 | 11.4.4 |
| `georgringer/news` | Packagist | From 12.0.0 | 12.3.2 |
| `georgringer/news` | Packagist | From 12.0.0 | 12.3.2 |
| `georgringer/news` | Packagist | From 13.0.0 | 13.0.2 |
| `georgringer/news` | Packagist | From 13.0.0 | 13.0.2 |
| `georgringer/news` | Packagist | From 14.0.0 | 14.0.3 |
| `georgringer/news` | Packagist | From 14.0.0 | 14.0.3 |

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

Upgrade georgringer/news to a fixed version for your release line: 10.0.4, 11.4.4, 12.3.2 or 13.0.2.

## Is CVE-2026-8726 being exploited?

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

Public exploit code:

- Minimal security backport for CVE-2026-8726 in georgringer/news 8.6.0 (github_poc): https://github.com/Shentao83/news-8.6.0-cve-2026-8726-backport

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8726 is a high-severity SQL injection vulnerability in TYPO3 Extension "News system", published on 19 May 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-8726 in the wild and no public exploit code.

Affected packages and fixed versions:
- georgringer/news (Packagist): affected all versions; fixed in 10.0.4
- georgringer/news (Packagist): affected all versions; fixed in 10.0.4
- georgringer/news (Packagist): affected from 11.0.0; fixed in 11.4.4
- georgringer/news (Packagist): affected from 11.0.0; fixed in 11.4.4
- georgringer/news (Packagist): affected from 12.0.0; fixed in 12.3.2
- georgringer/news (Packagist): affected from 12.0.0; fixed in 12.3.2
- georgringer/news (Packagist): affected from 13.0.0; fixed in 13.0.2
- georgringer/news (Packagist): affected from 13.0.0; fixed in 13.0.2
- georgringer/news (Packagist): affected from 14.0.0; fixed in 14.0.3
- georgringer/news (Packagist): affected from 14.0.0; fixed in 14.0.3

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

## Sources

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

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