TYPO3 CMS Allows Broken Access Control in Edit Document Controller
Published 13 Jan 2026 · Updated 3 Feb 2026
Affected packages
- Affected
- >=14.0.0 <14.0.2
- Fixed in
- 14.0.2
composer require typo3/cms-backend:^14.0.2- Affected
- >=13.0.0 <13.4.23
- Fixed in
- 13.4.23
composer require typo3/cms-backend:^13.4.23- Affected
- >=12.0.0 <12.4.41
- Fixed in
- 12.4.41
composer require typo3/cms-backend:^12.4.41- Affected
- >=11.0.0 <11.5.49
- Fixed in
- 11.5.49
composer require typo3/cms-backend:^11.5.49- Affected
- >=10.0.0 <10.4.55
- Fixed in
- 10.4.55
composer require typo3/cms-backend:^10.4.55Details
Problem
By exploiting the defVals parameter, attackers could bypass field‑level access checks during record creation in the TYPO3 backend. This gave them the ability to insert arbitrary data into prohibited exclude fields of a database table for which the user already has write permission for a reduced set of fields.
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 Daniel Windloff for reporting this issue, and to TYPO3 core & security team member Benjamin Franzke for fixing it.
References
Is GHSA-5j7q-wmh7-cqhg in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-backend, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/security/advisories/GHSA-5j7q-wmh7-cqhg
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-59020
- Linkgithub.com/TYPO3/typo3/commit/ac3f792bd5ab7c58153fc1075cb9e001c9cebe3b
- Linkgithub.com/TYPO3/typo3/commit/cd11a19958d823d12d028f9345b41739c7e70118
- Linkgithub.com/TYPO3/typo3/commit/fb98378a8fd30dd50d89a3d1a420780819f38232
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2026-001
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.