CVE-2025-59022: TYPO3 CMS Allows Broken Access Control in Recycler Module
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
Other sources
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. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-59022?
CVE-2025-59022 has a high severity rating due to its potential to allow unauthorized deletion of critical data.
Who is affected by CVE-2025-59022?
CVE-2025-59022 affects TYPO3 CMS versions from 10.0.0 to 14.0.1 that have users with access to the recycler module.
How do I fix CVE-2025-59022?
To fix CVE-2025-59022, update TYPO3 CMS to a version that patches this vulnerability as soon as possible.
What does CVE-2025-59022 allow attackers to do?
CVE-2025-59022 allows attackers to delete arbitrary data from any database table within TYPO3 CMS regardless of user permissions.
Is there a workaround for CVE-2025-59022?
Currently, there are no official workarounds for CVE-2025-59022; the recommended action is to apply available security patches.