CVE-2026-6553: TYPO3 CMS · Cleartext Storage of Sensitive Information
Affects TYPO3 CMSSource CVE Database V5
Not known to be exploited · CVSS 7.3 High : upgrade to 14.3.0 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 14.3.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade TYPO3 CMS and typo3/cms-backend to 14.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
GitHubtypo3/typo3pkg:github/typo3/typo3Other threats | Affected
| Fixed in– |
Packagisttypo3/cms-backendpkg:composer/typo3/cms-backendOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, administrators should limit database access strictly and monitor for unauthorized access. Avoid using the affected TYPO3 CMS version 14.2.0 for sensitive environments or consider mitigating by not changing passwords via the user settings module if possible. Follow vendor updates closely for an official fix.
Description
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.