TYPO3 Cross-Site Request Forgery in Backend User Module
Published 14 Jan 2025 · Updated 20 May 2025
Affected packages
- Affected
- >=10.0.0 <10.4.48
- Fixed in
- 10.4.48
composer require typo3/cms-beuser:^10.4.48- Affected
- >=11.0.0 <11.5.42
- Fixed in
- 11.5.42
composer require typo3/cms-beuser:^11.5.42- Affected
- >=12.0.0 <12.4.25
- Fixed in
- 12.4.25
composer require typo3/cms-beuser:^12.4.25- Affected
- >=13.0.0 <13.4.3
- Fixed in
- 13.4.3
composer require typo3/cms-beuser:^13.4.3Details
Problem
A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method.
Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions:
- the user opens a malicious link, such as one sent via email.
- the user visits a compromised or manipulated website while the following settings are misconfigured:
+
security.backend.enforceReferrerfeature is disabled, +BE/cookieSameSiteconfiguration is set tolaxornone
The vulnerability in the affected downstream component “Backend User Module” allows attackers to initiate password resets for other backend users or to terminate their user sessions.
Solution
Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.
Credits
Thanks to Gabriel Dimitrov who reported this issue and to TYPO3 core and security members Benjamin Franzke, Oliver Hader, Andreas Kienast, Torben Hansen, Elias Häußler who fixed the issue.
Is GHSA-6w4x-gcx3-8p7v 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-beuser, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/security/advisories/GHSA-6w4x-gcx3-8p7v
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-55894
- Linkgithub.com/TYPO3-CMS/beuser/commit/18603efc3a66d3255fdd04eb6bda6b4d6a95abea
- Linkgithub.com/TYPO3-CMS/beuser/commit/1bb317cb2bc0b2f6ba4f758a088f060b36c67f9d
- Linkgithub.com/TYPO3-CMS/beuser/commit/4142112a878f8805234729751bc6b9c0091560ab
- Packagegithub.com/TYPO3-CMS/beuser
- Linktypo3.org/security/advisory/typo3-core-sa-2025-004
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.