CVE-2026-6553
highpriority · track · 30OT risk · elevatedEPSS 0.002 · 6 %ileDEEUUSEPSS · scored 2026-10-27
Changing backend users' passwords via the user settings module results in storing the cleartext password in the uc and user_settings fields of the be_users database table. This issue affects TYPO3 CMS version 14.2.0.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 4.4–7.5
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-1191TYPO3 Core: Schwachstelle ermöglicht Offenlegung von InformationenDeutsch2026-04-20csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann eine Schwachstelle in TYPO3 Core ausnutzen, um Informationen offenzulegen.
- GHSA-xvv6-p4wf-mvx7TYPO3 CMS Stores Cleartext Password in User Settings Module2026-04-24ghsa · osvUS
### 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (6)
External citations — patches, advisories, analysis.
- https://nvd.nist.gov/vuln/detail/CVE-2026-6553cnnvd
- https://typo3.org/security/advisory/typo3-core-sa-2026-005Patchcnnvd
- https://github.com/TYPO3/typo3/commit/9a6e913f70767f63b322ae3e2d2f4e302624c291enisa_euvd
- https://typo3.org/security/advisory/typo3-core-sa-2026-005enisa_euvd
- https://github.com/TYPO3/typo3/commit/9a6e913f70767f63b322ae3e2d2f4e302624c291Patchnvd
- https://typo3.org/security/advisory/typo3-core-sa-2026-005Vendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan