# CVE-2026-6553: TYPO3 CMS Stores Cleartext Password in User Settings Module

> TYPO3 CMS stores cleartext passwords in the database when changed via user settings, exposing sensitive credentials to attackers with database access.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-xvv6-p4wf-mvx7

## What is CVE-2026-6553?

CVE-2026-6553 is a high-severity vulnerability in Typo3 Typo3, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### 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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-6553?

2 open source packages ship an affected version, including typo3/cms-backend. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms-backend` | Packagist | From 14.2.0 | 14.3.0 |
| `typo3/cms-backend` | Packagist | From 14.2.0 | 14.3.0 |

Products: Typo3 Typo3.

## How do I fix CVE-2026-6553?

Upgrade typo3/cms-backend to 14.3.0 or later.

## Is CVE-2026-6553 being exploited?

There is no known exploitation of CVE-2026-6553 in the wild and no public exploit code.

## Other vulnerabilities in Typo3 Typo3

- [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0)
- [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8)
- [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8)
- [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8)
- [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6553 and fix it if it is affected.

What it is: CVE-2026-6553 is a high-severity vulnerability in Typo3 Typo3, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-6553 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms-backend (Packagist): affected from 14.2.0; fixed in 14.3.0
- typo3/cms-backend (Packagist): affected from 14.2.0; fixed in 14.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6553/ (Markdown: https://insights.sbomify.com/CVE-2026-6553/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6553
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6553
- OSV: https://osv.dev/vulnerability/CVE-2026-6553

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6553/
Summaries are generated and may contain mistakes; the official description above is the record.