CVE-2025-59022
highpriority · track · 32OT risk · elevatedEPSS 0.004 · 36 %ileDEEUNLUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 4.9–8.1
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (27)
Products and version ranges known to be affected.
advisories (3)
Vendor and ecosystem advisories describing this.
- NCSC-2026-0018Kwetsbaarheden verholpen in TYPO3 CMSNL2026-01-16csaf · ncsc_nlNL
TYPO3 heeft kwetsbaarheden verholpen in TYPO3 CMS (Specifiek voor bepaalde versies).
- WID-SEC-W-2026-0095TYPO3 Core: Mehrere SchwachstellenDeutsch2026-01-13csaf · cert_bundDE
Ein entfernter, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, um potenziell Phishing-Angriffe durchzuführen oder einen Denial-of-Service-Zustand zu erzeugen.
- GHSA-p52w-7rhw-9m67TYPO3 CMS Allows Broken Access Control in Recycler Module2026-01-13ghsa · osvUS
### 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](https://typo3.org/security/advisory/typo3-core-sa-2026-003)
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (12)
External citations — patches, advisories, analysis.
- https://github.com/TYPO3/typo3/commit/336d6f165458a0ce32d8330999ab9ab6a5983d20cnnvd
- https://github.com/TYPO3/typo3/commit/a6604db66499710f72ae6e7006beb14ad0913aaecnnvd
- https://github.com/TYPO3/typo3/commit/efb9528f9882ac924c40598ebd8508479e9950a3cnnvd
- https://typo3.org/security/advisory/typo3-core-sa-2026-003cnnvd
- https://github.com/TYPO3/typo3/commit/336d6f165458a0ce32d8330999ab9ab6a5983d20enisa_euvd
- https://github.com/TYPO3/typo3/commit/a6604db66499710f72ae6e7006beb14ad0913aaeenisa_euvd
- https://github.com/TYPO3/typo3/commit/efb9528f9882ac924c40598ebd8508479e9950a3enisa_euvd
- https://typo3.org/security/advisory/typo3-core-sa-2026-003enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan