# GHSA-m96r-7vqm-j95g: Typo3 Information Disclosure in User Authentication

> Attackers can read plain-text user credentials from default warning logs during failed login attempts in TYPO3.

- **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-m96r-7vqm-j95g?

GHSA-m96r-7vqm-j95g is a 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

It has been discovered that login failures have been logged on the default stream with log level "warning" including plain-text user credentials.

## Which versions are affected by GHSA-m96r-7vqm-j95g?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 9.0.0 | 9.5.6 |
| `typo3/cms` | Packagist | From 9.0.0 | 9.5.6 |

## How do I fix GHSA-m96r-7vqm-j95g?

Upgrade typo3/cms to 9.5.6 or later.

## Is GHSA-m96r-7vqm-j95g being exploited?

There is no known exploitation of GHSA-m96r-7vqm-j95g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-m96r-7vqm-j95g and fix it if it is affected.

What it is: GHSA-m96r-7vqm-j95g is a 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-m96r-7vqm-j95g in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.6
- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.5.6

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-m96r-7vqm-j95g/ (Markdown: https://insights.sbomify.com/GHSA-m96r-7vqm-j95g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-m96r-7vqm-j95g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-m96r-7vqm-j95g/
Summaries are generated and may contain mistakes; the official description above is the record.