TYPO3 Unverified Password Change for Backend Users
Published 20 May 2025 · Updated 20 May 2025
Is your project on an affected typo3/cms-core?
Affected packages
- Affected
- >=9.0.0 <9.5.51
- Fixed in
- 9.5.51
composer require typo3/cms-core:^9.5.51- Affected
- >=9.0.0 <9.5.51
- Fixed in
- 9.5.51
composer require typo3/cms-setup:^9.5.51- Affected
- >=10.0.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.12- Affected
- >=10.0.0 <10.4.50
- Fixed in
- 10.4.50
composer require typo3/cms-setup:^10.4.50- Affected
- >=11.0.0 <11.5.44
- Fixed in
- 11.5.44
composer require typo3/cms-setup:^11.5.44- Affected
- >=12.0.0 <12.4.31
- Fixed in
- 12.4.31
composer require typo3/cms-setup:^12.4.31- Affected
- >=13.0.0 <13.4.12
- Fixed in
- 13.4.12
composer require typo3/cms-setup:^13.4.12Details
Problem
The backend user management interface allows password changes without requiring the current password. When an administrator updates their own account or modifies other user accounts via the admin interface, the current password is not requested for verification.
This behavior may lower the protection against unauthorized access in scenarios where an admin session is hijacked or left unattended, as it enables password changes without additional authentication.
Solution
Update to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.
> [!NOTE] > In these versions, administrators are required to verify their identity through step-up authentication (also known as sudo mode) when changing backend user passwords.
Credits
Thanks to the National Cyber Security Center (NCSC) of Switzerland for reporting this issue, and to TYPO3 core & security team member Benjamin Franzke for fixing it.
Is GHSA-3jrg-97f3-rqh9 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.
More advisories for typo3/cms-core
- HighCVE-2026-19418TYPO3 CMS - Broken Access Control in Backend and Install Tool · 1 Sept 2026
- HighCVE-2026-11607TYPO3 CMS has Broken Access Control in its Form Framework · 12 Jun 2026
- MediumCVE-2026-47349TYPO3 CMS has Broken Access Control in the Recycler Module · 12 Jun 2026
- MediumCVE-2026-47347TYPO3 CMS has an Open Redirect Vulnerability via Core Utilities · 12 Jun 2026
- HighCVE-2026-47343TYPO3 CMS: Destructive Actions on File Mount Folders · 12 Jun 2026
- HighCVE-2026-49741TYPO3 CMS has Privilege Escalation & SQL Injection in its Form Framework · 12 Jun 2026
References
- Linkgithub.com/TYPO3/typo3/security/advisories/GHSA-3jrg-97f3-rqh9
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-47938
- Linkgithub.com/TYPO3-CMS/core/commit/b9a8bcb614ecdd42aa27e1c430c6213d6b6b20b3
- Linkgithub.com/TYPO3-CMS/setup/commit/60572dd050d8d861921889a19599bfe045fed5fd
- Linktypo3.org/security/advisory/typo3-core-sa-2025-013
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.