Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Passwords were stored in cleartext in the uc and user_settings fields of the be_users table in typo3/cms-backend versions >=14.2.0, <14.3.0. The cleartext values were only saved when backend users changed their credentials in the user settings module, and the advisory does not describe the attacker's access requirements. Upgrade to 14.3.0, then run the User Settings Scrubbing upgrade wizard in the Install Tool and assign new passwords to affected backend accounts.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.3 | High | 4.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:H | CNA (TYPO3) |
- CISA KEV Not listed.
- EPSS 0.0017, the 5th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:25 UTC First seen by agentprime
- 31 Oct 2026, 14:25 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-xvv6-p4wf-mvx7
- OSV: GHSA-xvv6-p4wf-mvx7
- github.com/TYPO3/typo3/security/advisories/GHSA-xvv6-p4wf-mvx7
- nvd.nist.gov/vuln/detail/CVE-2026-6553
- github.com/TYPO3/typo3/commit/9a6e913f70767f63b322ae3e2d2f4e302624c291
- github.com/TYPO3/typo3
- typo3.org/security/advisory/typo3-core-sa-2026-005