CVE-2026-6553 json
TYPO3 CMS Stores Cleartext Password in User Settings Module
published 2026-04-21 6 mo ago modified 2026-10-25 14 d ago also GHSA-xvv6-p4wf-mvx7 , EUVD-2026-24081
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H |
| CNA | 4.0 | 7.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms-backend | >=14.2.0, <14.3.0 |
14.3.0 |
Affected products
- TYPO3 TYPO3 CMS
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
github.com
/TYPO3/typo3/commit/9a6e913f70767f63b322ae3e2d2f4e302624c291
patch, web
-
typo3.org
/security/advisory/typo3-core-sa-2026-005
vendor-advisory, web
-
github.com
/TYPO3/typo3/security/advisories/GHSA-xvv6-p4wf-mvx7
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-6553
advisory
-
github.com
/TYPO3/typo3
package
Sources
- CVE List CVE-2026-6553
- GitHub Advisory GHSA-xvv6-p4wf-mvx7
- NVD CVE-2026-6553
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.