# GHSA-mh3r-6cp5-hc2j: Authentication Bypass in TYPO3 Frontend

> Attackers can bypass authentication restrictions to log in as disabled frontend users in TYPO3 due to late TCA initialization.

- **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-mh3r-6cp5-hc2j?

GHSA-mh3r-6cp5-hc2j 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

Due to late TCA initialization the authentication service fails to restrict frontend user according to the validation rules. Therefore it is possible to authenticate restricted (e.g. disabled) frontend users.

## Which versions are affected by GHSA-mh3r-6cp5-hc2j?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 8.2.0 | 8.6.1 |
| `typo3/cms` | Packagist | From 8.2.0 | 8.6.1 |

## How do I fix GHSA-mh3r-6cp5-hc2j?

Upgrade typo3/cms to 8.6.1 or later.

## Is GHSA-mh3r-6cp5-hc2j being exploited?

There is no known exploitation of GHSA-mh3r-6cp5-hc2j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-mh3r-6cp5-hc2j and fix it if it is affected.

What it is: GHSA-mh3r-6cp5-hc2j 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-mh3r-6cp5-hc2j in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 8.2.0; fixed in 8.6.1
- typo3/cms (Packagist): affected from 8.2.0; fixed in 8.6.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-mh3r-6cp5-hc2j/ (Markdown: https://insights.sbomify.com/GHSA-mh3r-6cp5-hc2j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-mh3r-6cp5-hc2j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-mh3r-6cp5-hc2j/
Summaries are generated and may contain mistakes; the official description above is the record.