TYPO3 Allows Privilege Escalation to System Maintainer
Published 20 May 2025 · Updated 20 May 2025
Affected packages
- Affected
- >=10.4.0 <10.4.50
- Fixed in
- 10.4.50
composer require typo3/cms-core:^10.4.50- Affected
- >=11.0.0 <11.5.44
- Fixed in
- 11.5.44
composer require typo3/cms-core:^11.5.44- Affected
- >=12.0.0 <12.4.31
- Fixed in
- 12.4.31
composer require typo3/cms-core:^12.4.31- Affected
- >=13.0.0 <13.4.12
- Fixed in
- 13.4.12
composer require typo3/cms-core:^13.4.12Details
Problem
Administrator-level backend users without system maintainer privileges can escalate their privileges and gain system maintainer access. Exploiting this vulnerability requires a valid administrator account.
Solution
Update to TYPO3 versions 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.
Credits
Thanks to Alexander Künzl for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.
Is GHSA-6frx-j292-c844 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-core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.