CVE-2025-47938: TYPO3 Vulnerable to Unverified Password Change for Backend Users

Published May 20, 2025
·
Updated

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.

Other sources

TYPO3 is an open source, PHP based web content management system. Starting in version 9.0.0 and prior to versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, and 13.4.12 LTS, 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. Users should update to TYPO3 version 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS to fix the problem.

NVD

Affected Software

16 affected componentsFixes available
Typo3 TYPO3>=9.0.0<9.5.51, >=10.4.0<10.4.50, >=11.5.0<11.5.44, >=12.4.0<12.4.31, >=13.4.0<13.4.12
composer/typo3/cms-setup>=13.0.0<=13.4.11
13.4.12
composer/typo3/cms-setup>=12.0.0<=12.4.30
12.4.31
composer/typo3/cms-setup>=11.0.0<=11.5.43
11.5.44
composer/typo3/cms-setup>=10.0.0<=10.4.49
10.4.50
composer/typo3/cms-core>=13.0.0<=13.4.11
13.4.12
composer/typo3/cms-core>=12.0.0<=12.4.30
12.4.31
composer/typo3/cms-core>=11.0.0<=11.5.43
11.5.44
composer/typo3/cms-core>=10.0.0<=10.4.49
10.4.50
composer/typo3/cms-setup>=9.0.0<=9.5.50
9.5.51
composer/typo3/cms-core>=9.0.0<=9.5.50
9.5.51
Typo3 TYPO3>=9.0.0<9.5.51
Typo3 TYPO3>=10.0.0<10.4.50
Typo3 TYPO3>=11.0.0<11.5.44
Typo3 TYPO3>=12.0.0<12.4.31
Typo3 TYPO3>=13.0.0<13.4.12

Event History

May 20, 2025
CVE Published
via MITRE·01:49 PM
Data Sourced
via MITRE·01:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
Affected Software
Advisory Published
via GitHub·07:26 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-47938?

CVE-2025-47938 is classified as a critical vulnerability due to its impact on backend user management in TYPO3.

2

How do I fix CVE-2025-47938?

To fix CVE-2025-47938, upgrade TYPO3 to versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS.

3

What systems are affected by CVE-2025-47938?

CVE-2025-47938 affects TYPO3 versions from 9.0.0 up to 9.5.51 ELTS, 10.4.0 up to 10.4.50 ELTS, 11.5.0 up to 11.5.44 ELTS, 12.4.0 up to 12.4.31 LTS, and 13.4.0 up to 13.4.12 LTS.

4

What is the main issue caused by CVE-2025-47938?

CVE-2025-47938 allows backend users to change their passwords without providing the current password, leading to potential unauthorized access.

5

What should I do if I cannot upgrade immediately for CVE-2025-47938?

If an immediate upgrade is not possible for CVE-2025-47938, consider implementing strong access controls and monitoring user activities until a patch can be applied.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203