What is CVE-2025-59022?

CVE-2025-59022 is a high-severity missing authorization vulnerability in typo3/cms-recycler (composer), affecting versions >= 14.0.0, <= 14.0.1. It is fixed in 14.0.2, 13.4.23, 12.4.41, 11.5.49, 10.4.55. The application does not perform an authorization check before performing a sensitive operation.

Which versions of typo3/cms-recycler are affected by CVE-2025-59022?

typo3/cms-recycler (composer) versions >= 14.0.0, <= 14.0.1 is affected.

Is there a fix for CVE-2025-59022?

Yes. CVE-2025-59022 is fixed in 14.0.2, 13.4.23, 12.4.41, 11.5.49, 10.4.55. Upgrade to this version or later.

Is CVE-2025-59022 exploitable, and should I be worried?

Whether CVE-2025-59022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-59022 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-59022?

Upgrade: typo3/cms-recycler to 14.0.2 or later, typo3/cms-recycler to 13.4.23 or later, typo3/cms-recycler to 12.4.41 or later, typo3/cms-recycler to 11.5.49 or later, typo3/cms-recycler to 10.4.55 or later.

CVE-2025-59022 in typo3/cms-recycler

Q: Which versions of typo3/cms-recycler are affected by CVE-2025-59022?

typo3/cms-recycler (composer) versions >= 14.0.0, <= 14.0.1 is affected.

Q: Is there a fix for CVE-2025-59022?

Yes. CVE-2025-59022 is fixed in 14.0.2, 13.4.23, 12.4.41, 11.5.49, 10.4.55. Upgrade to this version or later.

Q: Is CVE-2025-59022 exploitable, and should I be worried?

Whether CVE-2025-59022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-59022 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-59022?

Upgrade: typo3/cms-recycler to 14.0.2 or later, typo3/cms-recycler to 13.4.23 or later, typo3/cms-recycler to 12.4.41 or later, typo3/cms-recycler to 11.5.49 or later, typo3/cms-recycler to 10.4.55 or later.

Summary

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.

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

Impact

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Affected versions

typo3/cms-recycler (>= 14.0.0, <= 14.0.1) typo3/cms-recycler (>= 13.0.0, <= 13.4.22) typo3/cms-recycler (>= 12.0.0, <= 12.4.40) typo3/cms-recycler (>= 11.0.0, <= 11.5.48) typo3/cms-recycler (>= 10.0.0, <= 10.4.54)

Security releases

typo3/cms-recycler → 14.0.2 (composer) typo3/cms-recycler → 13.4.23 (composer) typo3/cms-recycler → 12.4.41 (composer) typo3/cms-recycler → 11.5.49 (composer) typo3/cms-recycler → 10.4.55 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2025-59022? CVE-2025-59022 is a high-severity missing authorization vulnerability in typo3/cms-recycler (composer), affecting versions >= 14.0.0, <= 14.0.1. It is fixed in 14.0.2, 13.4.23, 12.4.41, 11.5.49, 10.4.55. The application does not perform an authorization check before performing a sensitive operation.
Which versions of typo3/cms-recycler are affected by CVE-2025-59022? typo3/cms-recycler (composer) versions >= 14.0.0, <= 14.0.1 is affected.
Is there a fix for CVE-2025-59022? Yes. CVE-2025-59022 is fixed in 14.0.2, 13.4.23, 12.4.41, 11.5.49, 10.4.55. Upgrade to this version or later.
Is CVE-2025-59022 exploitable, and should I be worried? Whether CVE-2025-59022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-59022 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-59022?
- Upgrade typo3/cms-recycler to 14.0.2 or later
- Upgrade typo3/cms-recycler to 13.4.23 or later
- Upgrade typo3/cms-recycler to 12.4.41 or later
- Upgrade typo3/cms-recycler to 11.5.49 or later
- Upgrade typo3/cms-recycler to 10.4.55 or later

Other vulnerabilities in typo3/cms-recycler

CVE-IDSeverityPackage summary

CVE-2026-47349Mediumtypo3/cms-core: TYPO3 CMS has Broken Access Control in the Recycler Module CVE-2025-59017Mediumtypo3/cms-workspaces: TYPO3 backend modules have Broken Access Control