How severe is GHSA-p52w-7rhw-9m67?

No CVSS score has been assigned to GHSA-p52w-7rhw-9m67 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p52w-7rhw-9m67?

GHSA-p52w-7rhw-9m67 affects the following packages: typo3/cms-recycler (Packagist), typo3/cms-recycler (Packagist), typo3/cms-recycler (Packagist), typo3/cms-recycler (Packagist), typo3/cms-recycler (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p52w-7rhw-9m67?

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.

How do I detect GHSA-p52w-7rhw-9m67 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-recycler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p52w-7rhw-9m67 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-p52w-7rhw-9m67 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p52w-7rhw-9m67 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-p52w-7rhw-9m67?

GHSA-p52w-7rhw-9m67 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-p52w-7rhw-9m67?

GHSA-p52w-7rhw-9m67 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p52w-7rhw-9m67 published, and has it been updated?

GHSA-p52w-7rhw-9m67 was published on January 13, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

TYPO3 CMS Allows Broken Access Control in Recycler ModuleGHSA-p52w-7rhw-9m67

Fix: TYPO3/typo3@336d6f1

GHSA-p52w-7rhw-9m67 is a CWE-862 vulnerability in typo3/cms-recycler. A fix is available for typo3/cms-recycler — see the affected versions and patch details below.

Also known asCVE-2025-59022

Published

Jan 13, 2026

Updated

Feb 3, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p52w-7rhw-9m67.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

🐘typo3/cms-recycler🐘typo3/cms-recycler🐘typo3/cms-recycler🐘typo3/cms-recycler🐘typo3/cms-recycler

Real-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

TYPO3-CORE-SA-2026-003

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-recycler`	≥ 14.0.0&&< 14.0.2	14.0.2`composer require typo3/cms-recycler:^14.0.2`
🐘Packagist	`typo3/cms-recycler`	≥ 13.0.0&&< 13.4.23	13.4.23`composer require typo3/cms-recycler:^13.4.23`
🐘Packagist	`typo3/cms-recycler`	≥ 12.0.0&&< 12.4.41	12.4.41`composer require typo3/cms-recycler:^12.4.41`
🐘Packagist	`typo3/cms-recycler`	≥ 11.0.0&&< 11.5.49	11.5.49`composer require typo3/cms-recycler:^11.5.49`
🐘Packagist	`typo3/cms-recycler`	≥ 10.0.0&&< 10.4.55	10.4.55`composer require typo3/cms-recycler:^10.4.55`

Affected Products

1 product · 5 configurations

Application

typo3typo3

≥ 14.0.0 && < 14.0.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-recycler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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. ### Re

O3 Security · Impact-Aware SCA

Is GHSA-p52w-7rhw-9m67 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works