# TYPO3 CMS has Broken Access Control in its DataHandler

Advisory record · `GHSA-qcmw-6rm2-5x78`

- **Identifiers:** `GHSA-qcmw-6rm2-5x78` · `CVE-2026-47350` · `PKSA-vv7s-w171-wb2j`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 12 Jun 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 12 Jun 2026, 19:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `typo3/cms-core` (Packagist): affected `>=13.0.0, <13.4.31 || >=14.0.0, <14.3.3`; fixed in `13.4.31`, `14.3.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> TYPO3 CMS core (Packagist package typo3/cms-core) versions from 13.0.0 before 13.4.31 and from 14.0.0 before 14.3.3 are affected. A backend user could move records to a different page without having edit permission on the source page, which is a broken access control flaw in the DataHandler. Upgrade to TYPO3 13.4.31 or 14.3.3, which fix the problem.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (TYPO3)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0024, the 14th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:00 UTC: First seen by agentprime
- 31 Oct 2026, 14:00 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qcmw-6rm2-5x78)

## Sources

- [GitHub Advisory Database: GHSA-qcmw-6rm2-5x78](https://github.com/advisories/GHSA-qcmw-6rm2-5x78)
- [OSV: GHSA-qcmw-6rm2-5x78](https://osv.dev/vulnerability/GHSA-qcmw-6rm2-5x78)
- <https://github.com/TYPO3/typo3/security/advisories/GHSA-qcmw-6rm2-5x78>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-47350>
- <https://github.com/TYPO3/typo3/commit/195356996a60e40aeb2cd3e45a5f5c8940d5e116>
- <https://github.com/TYPO3/typo3/commit/c9898d2e67608eda78f8bd1f06ee9cf05a872a56>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-47350.yaml>
- <https://github.com/TYPO3/typo3>
- <https://typo3.org/security/advisory/typo3-core-sa-2026-012>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qcmw-6rm2-5x78>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qcmw-6rm2-5x78/>. Everything for agents: <https://agentprime.io/llms.txt>.
