TYPO3 CMS Allows Broken Access Control in Recycler Module
Published 13 Jan 2026 · Updated 3 Feb 2026
Affected packages
- Affected
- >=14.0.0 <14.0.2
- Fixed in
- 14.0.2
composer require typo3/cms-recycler:^14.0.2- Affected
- >=13.0.0 <13.4.23
- Fixed in
- 13.4.23
composer require typo3/cms-recycler:^13.4.23- Affected
- >=12.0.0 <12.4.41
- Fixed in
- 12.4.41
composer require typo3/cms-recycler:^12.4.41- Affected
- >=11.0.0 <11.5.49
- Fixed in
- 11.5.49
composer require typo3/cms-recycler:^11.5.49- Affected
- >=10.0.0 <10.4.55
- Fixed in
- 10.4.55
composer require typo3/cms-recycler:^10.4.55Details
Problem
Backend users who had access to the recycler module could delete arbitrary data from any database table defined in the TCA - regardless of whether they had permission to that particular table. This allowed attackers to purge and destroy critical site data, effectively rendering the website unavailable.
Solution
Update to TYPO3 versions 10.4.55 ELTS, 11.5.49 ELTS, 12.4.41 LTS, 13.4.23 LTS, 14.0.2 that fix the problem described.
Credits
Thanks to Sven Jürgens and Daniel Windloff for reporting this issue, and to TYPO3 security team member Elias Häußler for fixing it.
References
Is GHSA-p52w-7rhw-9m67 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-recycler, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/security/advisories/GHSA-p52w-7rhw-9m67
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-59022
- Linkgithub.com/TYPO3/typo3/commit/336d6f165458a0ce32d8330999ab9ab6a5983d20
- Linkgithub.com/TYPO3/typo3/commit/a6604db66499710f72ae6e7006beb14ad0913aae
- Linkgithub.com/TYPO3/typo3/commit/efb9528f9882ac924c40598ebd8508479e9950a3
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2026-003
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.