GHSA-p52w-7rhw-9m67
Fix: TYPO3/typo3@336d6f1GHSA-p52w-7rhw-9m67 is a CWE-862 vulnerability in typo3/cms-recycler. O3 Security confirms whether GHSA-p52w-7rhw-9m67 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
TYPO3 CMS Allows Broken Access Control in Recycler Module
Real-World Exposure
typo3/cms-recycler🐘typo3/cms-recycler🐘typo3/cms-recycler🐘typo3/cms-recycler🐘typo3/cms-recyclerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-recycler | ≥ 14.0.0&&< 14.0.2 | 14.0.2 |
| 🐘Packagist | typo3/cms-recycler | ≥ 13.0.0&&< 13.4.23 | 13.4.23 |
| 🐘Packagist | typo3/cms-recycler | ≥ 12.0.0&&< 12.4.41 | 12.4.41 |
| 🐘Packagist | typo3/cms-recycler | ≥ 11.0.0&&< 11.5.49 | 11.5.49 |
| 🐘Packagist | typo3/cms-recycler | ≥ 10.0.0&&< 10.4.55 | 10.4.55 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-recycler. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update typo3/cms-recycler to 14.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p52w-7rhw-9m67 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-p52w-7rhw-9m67 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-p52w-7rhw-9m67. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p52w-7rhw-9m67 in your dependencies?
O3 detects GHSA-p52w-7rhw-9m67 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.