CVE-2025-47938

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.

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.

CVE-2025-47938 has a CVSS score of 3.8 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2025-47938? CVE-2025-47938 is a low-severity security vulnerability in typo3/cms-core (composer), affecting versions >= 9.0.0, <= 9.5.50. It is fixed in 9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12.
2. How severe is CVE-2025-47938? CVE-2025-47938 has a CVSS score of 3.8 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-47938?
   • typo3/cms-core (composer) (versions >= 9.0.0, <= 9.5.50)
   • typo3/cms-setup (composer) (versions >= 9.0.0, <= 9.5.50)
4. Is there a fix for CVE-2025-47938? Yes. CVE-2025-47938 is fixed in 9.5.51, 10.4.50, 11.5.44, 12.4.31, 13.4.12. Upgrade to this version or later.
5. Is CVE-2025-47938 exploitable, and should I be worried? Whether CVE-2025-47938 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-47938 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-47938?
   • Upgrade typo3/cms-core to 9.5.51 or later
   • Upgrade typo3/cms-setup to 9.5.51 or later
   • Upgrade typo3/cms-core to 10.4.50 or later
   • Upgrade typo3/cms-core to 11.5.44 or later
   • Upgrade typo3/cms-core to 12.4.31 or later
   • Upgrade typo3/cms-core to 13.4.12 or later
   • Upgrade typo3/cms-setup to 10.4.50 or later
   • Upgrade typo3/cms-setup to 11.5.44 or later
   • Upgrade typo3/cms-setup to 12.4.31 or later
   • Upgrade typo3/cms-setup to 13.4.12 or later