TYPO3 CMS Allows Broken Access Control in Recycler Module
CVE-2025-59022GHSA-p52w-7rhw-9m67
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms-recycler 14.0.2, 13.4.23, 12.4.41, 11.5.49, 10.4.55), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist typo3/cms-recycler
- Affected
- >= 14.0.0, <= 14.0.1>= 13.0.0, <= 13.4.22>= 12.0.0, <= 12.4.40>= 11.0.0, <= 11.5.48>= 10.0.0, <= 10.4.54
- Fixed in
- 11.5.49, 10.4.55, 13.4.23, 14.0.2, 12.4.41
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-p52w-7rhw-9m67 lists affected ranges: Packagist typo3/cms-recycler >=14.0.0 =13.0.0 =12.0.0 =11.0.0 =10.0.0 <=10.4.54
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2025-59022: 0.42% estimated exploitation activity in the next 30 days; percentile 36.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-p52w-7rhw-9m67
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-59022 Advisory: TYPO3 CMS Allows Broken Access Control in Recycler Module IDs: CVE-2025-59022, GHSA-p52w-7rhw-9m67 Record: https://patchnext.com/advisories/cve-2025-59022 (revision 1, source checked 26 Oct 2026, 14:35 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: typo3/cms-recycler 14.0.2, 13.4.23, 12.4.41, 11.5.49, 10.4.55. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist typo3/cms-recycler: affected >= 14.0.0, <= 14.0.1; >= 13.0.0, <= 13.4.22; >= 12.0.0, <= 12.4.40; >= 11.0.0, <= 11.5.48; >= 10.0.0, <= 10.4.54; fixed in 11.5.49, 10.4.55, 13.4.23, 14.0.2, 12.4.41 ## Suggested inspection (read-only) - Packagist typo3/cms-recycler: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on typo3/cms-recycler. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-p52w-7rhw-9m67 (GitHub-reviewed advisory GHSA-p52w-7rhw-9m67 lists affected ranges: Packagist typo3/cms-recycler >=14.0.0 =13.0.0 =12.0.0 =11.0.0 =10.0.0 <=10.4.54) Commands are suggestions: review each one before running it.
Loading voting…