CVE-2025-47938: TYPO3 Unverified Password Change for Backend Users
3.8
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.18981%
CWE
Published
5/20/2025
Updated
5/20/2025
KEV Status
No
Technology
PHP
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| typo3/cms-core | composer | >= 9.0.0, <= 9.5.50 | 9.5.51 |
| typo3/cms-setup | composer | >= 9.0.0, <= 9.5.50 | 9.5.51 |
| typo3/cms-core | composer | >= 10.0.0, <= 10.4.49 | 10.4.50 |
| typo3/cms-core | composer | >= 11.0.0, <= 11.5.43 | 11.5.44 |
| typo3/cms-core | composer | >= 12.0.0, <= 12.4.30 | 12.4.31 |
| typo3/cms-core | composer | >= 13.0.0, <= 13.4.11 | 13.4.12 |
| typo3/cms-setup | composer | >= 10.0.0, <= 10.4.49 | 10.4.50 |
| typo3/cms-setup | composer | >= 11.0.0, <= 11.5.43 | 11.5.44 |
| typo3/cms-setup | composer | >= 12.0.0, <= 12.4.30 | 12.4.31 |
| typo3/cms-setup | composer | >= 13.0.0, <= 13.4.11 | 13.4.12 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability allows changing backend user passwords without verifying the current password. This issue manifested in two primary ways:
- In the 'User Setup' module, handled by
TYPO3\CMS\Setup\Controller\SetupModuleController::storeIncomingData. The existing logic for checking the current password was insufficient or could be bypassed, particularly for admin users. The patch removes this direct password checking logic. - In general backend user editing forms, where data is processed by
TYPO3\CMS\Core\DataHandling\DataHandler::process_datamap. TheDataHandlerrelied on TCA configurations, which, for thebe_users.passwordfield, did not mandate any specific authentication context (like current password check or step-up auth). The patch adds anauthenticationContextto the TCA for the password field.
Both functions were involved in processing password change requests without adequate verification. The patches introduce a system-wide step-up authentication requirement for such sensitive operations, moving away from direct (and flawed) current password checks within specific controllers or relying on TCA to enforce stricter authentication for the DataHandler.