# GHSA-6xh8-8pfv-53vx: Authentication Bypass in TYPO3 CMS

> Attackers can bypass authentication for backend and frontend users if database entries have empty passwords, typically caused by third-party components.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jun 2024

## What is GHSA-6xh8-8pfv-53vx?

GHSA-6xh8-8pfv-53vx is an authentication bypass vulnerability in typo3/cms, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default authentication service misses to invalidate empty strings as password. Therefore it is possible to authenticate backend and frontend users without password set in the database.
Note: TYPO3 does not allow to create user accounts without a password. Your TYPO3 installation might only be affected if there is a third party component creating user accounts without password by directly manipulating the database.

## Which versions are affected by GHSA-6xh8-8pfv-53vx?

6 open source packages ship an affected version, including typo3/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.20 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.20 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.5 |
| `typo3/cms` | Packagist | From 7.6.0 | 7.6.5 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.0.1 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.0.1 |

## How do I fix GHSA-6xh8-8pfv-53vx?

Upgrade typo3/cms to a fixed version for your release line: 6.2.20, 7.6.5 or 8.0.1.

## Is GHSA-6xh8-8pfv-53vx being exploited?

There is no known exploitation of GHSA-6xh8-8pfv-53vx in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6xh8-8pfv-53vx and fix it if it is affected.

What it is: GHSA-6xh8-8pfv-53vx is an authentication bypass vulnerability in typo3/cms, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-6xh8-8pfv-53vx in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.20
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.20
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.5
- typo3/cms (Packagist): affected from 7.6.0; fixed in 7.6.5
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.0.1
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.0.1

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/GHSA-6xh8-8pfv-53vx/ (Markdown: https://insights.sbomify.com/GHSA-6xh8-8pfv-53vx/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6xh8-8pfv-53vx

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6xh8-8pfv-53vx/
Summaries are generated and may contain mistakes; the official description above is the record.