CVE-2026-6553: TYPO3 CMS Stores Cleartext Password in User Settings Module
Problem The backend user settings module (SetupModuleController) incorrectly conflates entity data (like passwords or email address) with user-interface settings (like theme, display options) when persisting changes. As a result, passwords were stored in cleartext in the uc and usersettings fields of the beusers database table.
Published Apr 24, 2026 · Updated May 8, 2026
Affected packages
typo3/cms-backend
- Ecosystem
- Composer (PHP)
- Affected
- = 14.2.0
- Fixed in
- 14.3.0
- Check
composer show typo3/cms-backend
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Problem
The backend user settings module (SetupModuleController) incorrectly conflates entity data (like passwords or email address) with user-interface settings (like theme, display options) when persisting changes. As a result, passwords were stored in cleartext in the uc and user_settings fields of the be_users database table.
The cleartext data was only persisted if users changed their credentials in the backend user settings module when the TYPO3 14.2.0 release was used (not in any other version).
Solution
Update to TYPO3 version 14.3.0 LTS which fixes the problem described.
[!IMPORTANT] > Manual actions required > > Updating to the patched release does not retroactively clean existing data. It is recommended to execute all User Settings upgrade wizards in the TYPO3 Install Tool, including the dedicated User Settings Scrubbing wizard, which sanitizes the incorrectly persisted cleartext values from the uc and user_settings fields of the be_users table. Additionally, affected backend user accounts should be assigned new passwords. > > _Admin Tools → Upgrade → Upgrade Wizard → User Settings Scrubbing_
Credits
TYPO3 thanks Martin Clewing for reporting this issue, and TYPO3 core team members Oliver Hader, Stefan Bürk and Garvin Hicking for fixing it.
Credited to mclewing, garvinhicking, ohader.
References
- https://github.com/TYPO3/typo3/security/advisories/GHSA-xvv6-p4wf-mvx7
- https://nvd.nist.gov/vuln/detail/CVE-2026-6553
- https://github.com/TYPO3/typo3/commit/9a6e913f70767f63b322ae3e2d2f4e302624c291
- https://typo3.org/security/advisory/typo3-core-sa-2026-005
- https://github.com/advisories/GHSA-xvv6-p4wf-mvx7
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-19418
TYPO3 CMS - Broken Access Control in Backend and Install Tool
high7.3Sep 1, 2026CVE-2026-47351
TYPO3 CMS: Broken Access Control in Media Module
medium5.3Jun 12, 2026CVE-2026-47352
TYPO3 CMS has Broken Access Control in Backend API
medium5.3Jun 12, 2026CVE-2025-59020
TYPO3 CMS Allows Broken Access Control in Edit Document Controller
medium5.3Jan 13, 2026CVE-2025-59014
TYPO3 Bookmark Toolbar vulnerable to denial of service
medium5.1Sep 9, 2025CVE-2025-59017
TYPO3 backend modules have Broken Access Control
medium5.3Sep 9, 2025
