# TYPO3 CMS Allows Broken Access Control in Recycler Module

Advisory record · `GHSA-p52w-7rhw-9m67`

- **Identifiers:** `GHSA-p52w-7rhw-9m67` · `CVE-2025-59022` · `PKSA-kq4c-tzdn-3hmx`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **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:** 13 Jan 2026
- **Updated:** 3 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Jan 2026, 20:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `typo3/cms-recycler` (Packagist): affected `>=14.0.0, <14.0.2 || >=13.0.0, <13.4.23 || >=12.0.0, <12.4.41 || >=11.0.0, <11.5.49 || >=10.0.0, <10.4.55`; fixed in `14.0.2`, `13.4.23`, `12.4.41`, `11.5.49`, `10.4.55`

## Machine-written summary

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

> Versions of typo3/cms-recycler from 10.0.0 up to (not including) 10.4.55, 11.0.0 up to 11.5.49, 12.0.0 up to 12.4.41, 13.0.0 up to 13.4.23, and 14.0.0 up to 14.0.2 are affected. A backend user with access to the recycler module can delete data from any TCA-defined table, including tables they lack permission for, which can make the site unavailable. Upgrade to 10.4.55, 11.5.49, 12.4.41, 13.4.23, or 14.0.2.

Written 3 Nov 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

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

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

## Timeline

- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p52w-7rhw-9m67)

## Sources

- [GitHub Advisory Database: GHSA-p52w-7rhw-9m67](https://github.com/advisories/GHSA-p52w-7rhw-9m67)
- [OSV: GHSA-p52w-7rhw-9m67](https://osv.dev/vulnerability/GHSA-p52w-7rhw-9m67)
- <https://github.com/TYPO3/typo3/security/advisories/GHSA-p52w-7rhw-9m67>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-59022>
- <https://github.com/TYPO3/typo3/commit/336d6f165458a0ce32d8330999ab9ab6a5983d20>
- <https://github.com/TYPO3/typo3/commit/a6604db66499710f72ae6e7006beb14ad0913aae>
- <https://github.com/TYPO3/typo3/commit/efb9528f9882ac924c40598ebd8508479e9950a3>
- <https://github.com/TYPO3/typo3>
- <https://typo3.org/security/advisory/typo3-core-sa-2026-003>

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-p52w-7rhw-9m67>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p52w-7rhw-9m67/>. Everything for agents: <https://agentprime.io/llms.txt>.
