# TYPO3 CMS - Broken Access Control in Backend and Install Tool

Advisory record · `GHSA-68jx-f42c-7599`

- **Identifiers:** `GHSA-68jx-f42c-7599` · `CVE-2026-19418` · `PKSA-hf64-fs5s-6k3h` · `PKSA-nmd9-kc7m-nsvr`
- **State:** Confirmed
- **Severity:** CVSS 7.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-346](https://cwe.mitre.org/data/definitions/346.html) · [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md) · [CWE-346](https://agentprime.io/advisories/tag/cwe-346.md)
- **Published:** 1 Sept 2026
- **Updated:** 1 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Sept 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `typo3/cms-backend` (Packagist): affected `>=13.0.0, <13.4.34`; fixed in `13.4.34`
- `typo3/cms-core` (Packagist): affected `>=14.0.0, <14.3.6`; fixed in `14.3.6`

## 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

- 7.3 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (TYPO3)

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

## Timeline

- 31 Oct 2026, 14:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-68jx-f42c-7599)

## Sources

- [GitHub Advisory Database: GHSA-68jx-f42c-7599](https://github.com/advisories/GHSA-68jx-f42c-7599)
- [OSV: GHSA-68jx-f42c-7599](https://osv.dev/vulnerability/GHSA-68jx-f42c-7599)
- <https://github.com/TYPO3/typo3/security/advisories/GHSA-68jx-f42c-7599>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-19418>
- <https://github.com/TYPO3/typo3/commit/4a75e862c589c85d795d7c65dcdc835f8f413efc>
- <https://github.com/TYPO3/typo3/commit/a0e8ee06a40e959b9e7b06a4b1cb19d3a0d3dcf7>
- <https://github.com/TYPO3/typo3/commit/ae0abd329d52285fe6e92804c3608820ad45e872>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-19418.yaml>
- <https://github.com/TYPO3/typo3>
- <https://news.typo3.com/security/advisory/typo3-core-sa-2026-021>
- <https://typo3.org/security/advisory/typo3-core-sa-2020-006>
- <https://typo3.org/security/advisory/typo3-core-sa-2026-021>

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-68jx-f42c-7599>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-68jx-f42c-7599/>. Everything for agents: <https://agentprime.io/llms.txt>.