CVE-2025-47938 is a low-severity (CVSS 3.8) CWE-620 vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.
TYPO3 Vulnerable to Unverified Password Change for Backend Users
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-47938.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
typo3/cms-core🐘typo3/cms-setup🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-setup🐘typo3/cms-setup+2 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.51 | 9.5.51composer require typo3/cms-core:^9.5.51 |
| 🐘Packagist | typo3/cms-setup | ≥ 9.0.0&&< 9.5.51 | 9.5.51composer require typo3/cms-setup:^9.5.51 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.50 | 10.4.50composer require typo3/cms-core:^10.4.50 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.44 | 11.5.44composer require typo3/cms-core:^11.5.44 |
| 🐘Packagist | typo3/cms-core | ≥ 12.0.0&&< 12.4.31 | 12.4.31composer require typo3/cms-core:^12.4.31 |
| 🐘Packagist | typo3/cms-core | ≥ 13.0.0&&< 13.4.12 | 13.4.12composer require typo3/cms-core:^13.4.12 |
Affected Products
typo3typo3Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 9.5.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-47938 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2025-47938 in your dependencies?
Find it across Packagist, including transitive dependencies.