Vulnerability advisory

GHSA-p52w-7rhw-9m67

TYPO3 CMS Allows Broken Access Control in Recycler Module

Published Jan 13, 2026Updated Feb 3, 2026OSV record ↗

Also known as CVE-2025-59022

Severity

CVSS 4.0CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Affected versions

typo3/cms-recycler Packagist

All typo3/cms-recycler advisories →

Affected	Fixed in
`14.0.0` to before 14.0.2	`14.0.2`Advisories →
Also listed as affected (2) `v14.0.0` `v14.0.1`
`13.0.0` to before 13.4.23	`13.4.23`Advisories →
Also listed as affected (30) `v13.0.0` `v13.0.1` `v13.1.0` `v13.1.1` `v13.2.1` `v13.3.0` `v13.3.1` `v13.4.0` `v13.4.1` `v13.4.10` `v13.4.11` `v13.4.12` `v13.4.13` `v13.4.14` `v13.4.15` `v13.4.16` `v13.4.17` `v13.4.18` `v13.4.19` `v13.4.2` `v13.4.20` `v13.4.21` `v13.4.22` `v13.4.3` `v13.4.4` `v13.4.5` `v13.4.6` `v13.4.7` `v13.4.8` `v13.4.9`
`12.0.0` to before 12.4.41	`12.4.41`Advisories →
Also listed as affected (48) `v12.0.0` `v12.1.0` `v12.1.1` `v12.1.2` `v12.1.3` `v12.2.0` `v12.3.0` `v12.4.0` `v12.4.1` `v12.4.10` `v12.4.11` `v12.4.12` `v12.4.13` `v12.4.14` `v12.4.15` `v12.4.16` `v12.4.17` `v12.4.18` `v12.4.19` `v12.4.2` `v12.4.20` `v12.4.21` `v12.4.22` `v12.4.23` `v12.4.24` `v12.4.25` `v12.4.26` `v12.4.27` `v12.4.28` `v12.4.29` `v12.4.3` `v12.4.30` `v12.4.31` `v12.4.32` `v12.4.33` `v12.4.34` `v12.4.35` `v12.4.36` `v12.4.37` `v12.4.38` `v12.4.39` `v12.4.4` `v12.4.40` `v12.4.5` `v12.4.6` `v12.4.7` `v12.4.8` `v12.4.9`
`11.0.0` to before 11.5.49	`11.5.49`Advisories →
Also listed as affected (51) `v11.0.0` `v11.1.0` `v11.1.1` `v11.2.0` `v11.3.0` `v11.3.1` `v11.3.2` `v11.3.3` `v11.4.0` `v11.5.0` `v11.5.1` `v11.5.10` `v11.5.11` `v11.5.12` `v11.5.13` `v11.5.14` `v11.5.15` `v11.5.16` `v11.5.17` `v11.5.18` `v11.5.19` `v11.5.2` `v11.5.20` `v11.5.21` `v11.5.22` `v11.5.23` `v11.5.24` `v11.5.25` `v11.5.26` `v11.5.27` `v11.5.28` `v11.5.29` `v11.5.3` `v11.5.30` `v11.5.31` `v11.5.32` `v11.5.33` `v11.5.34` `v11.5.35` `v11.5.36` `v11.5.37` `v11.5.38` `v11.5.39` `v11.5.4` `v11.5.40` `v11.5.41` `v11.5.5` `v11.5.6` `v11.5.7` `v11.5.8` `v11.5.9`
`10.0.0` to before 10.4.55	`10.4.55`Advisories →
Also listed as affected (43) `v10.0.0` `v10.1.0` `v10.2.0` `v10.2.1` `v10.2.2` `v10.3.0` `v10.4.0` `v10.4.1` `v10.4.10` `v10.4.11` `v10.4.12` `v10.4.13` `v10.4.14` `v10.4.15` `v10.4.16` `v10.4.17` `v10.4.18` `v10.4.19` `v10.4.2` `v10.4.20` `v10.4.21` `v10.4.22` `v10.4.23` `v10.4.24` `v10.4.25` `v10.4.26` `v10.4.27` `v10.4.28` `v10.4.29` `v10.4.3` `v10.4.30` `v10.4.31` `v10.4.32` `v10.4.33` `v10.4.34` `v10.4.36` `v10.4.37` `v10.4.4` `v10.4.5` `v10.4.6` `v10.4.7` `v10.4.8` `v10.4.9`

Description

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

TYPO3-CORE-SA-2026-003