TYPO3 CMS: Cleartext Storage of Sensitive Information
CVE-2026-6553 is a high-severity cleartext storage of sensitive information vulnerability in TYPO3 CMS from TYPO3, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 14.3.0 as the first without the flaw, so updating TYPO3 CMS to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update TYPO3 CMS to 14.3.0 or a later version.
- Read the advisory on typo3.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| TYPO3 | TYPO3 CMS | 14.2.0 up to, but not including, 14.3.0 | 14.3.0 |
| TYPO3 | Typo3 | 14.2.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.3 | High | CNA |
| CVSS 3.1 | 7.5 | High | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Cleartext Storage of Sensitive Information
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
How developers prevent this class of flaw
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
- In some systems/environments such as cloud, the use of double encryption (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
More Cleartext Storage of Sensitive Information vulnerabilities (CWE-312)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other vulnerabilities in TYPO3 CMS
- 7.5 High severity
- 7.3 High severity
- 7.1 High severity
- 8.7 High severity
- 7.6 High severity
- 7.2 High severity
Recent Cleartext Storage of Sensitive Information vulnerabilities
- 9.3 Critical severity
- 7.5 High severity
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.