CVE-2026-6553: Changing backend users' passwords via the user settings module results in storing the cleartext password in th
CVE-2026-6553 is a high-severity flaw (CVSS 7.5) affecting typo3. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 94%) |
| CISA exploited list | No |
| Weakness | CWE-312 |
| Published | 2026-04-21 |
| Last modified | 2026-10-25 |
Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-6553?
typo3: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2026-6553 being exploited?
CVE-2026-6553 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-6553 affect?
CVE-2026-6553 affects typo3. Severity is high (CVSS 7.5). 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.
How urgent is CVE-2026-6553?
Priority 33/100. High severity; Remotely exploitable, no login, no user action