# TYPO3 Information Disclosure in User Authentication

Advisory record · `GHSA-wj85-rg5g-v8jm`

- **Identifiers:** `GHSA-wj85-rg5g-v8jm` · `PKSA-39st-t16f-w2cm`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-256](https://cwe.mitre.org/data/definitions/256.html)
- **Tags:** [CWE-256](https://agentprime.io/advisories/tag/cwe-256.md)
- **Published:** 30 May 2024
- **Updated:** 5 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 May 2024, 18:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `typo3/cms-core` (Packagist): affected `>=9.0.0, <9.5.6`; fixed in `9.5.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> TYPO3 typo3/cms-core versions 9.0.0 up to but not including 9.5.6 are affected. Login failures are logged at the default stream with log level "warning" and include plain-text user credentials, so anyone with access to those logs can read them. Upgrade typo3/cms-core to 9.5.6 or later. The source gives few details about who can read the logs.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:28 UTC: First seen by agentprime
- 31 Oct 2026, 14:28 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wj85-rg5g-v8jm)

## Sources

- [GitHub Advisory Database: GHSA-wj85-rg5g-v8jm](https://github.com/advisories/GHSA-wj85-rg5g-v8jm)
- [OSV: GHSA-wj85-rg5g-v8jm](https://osv.dev/vulnerability/GHSA-wj85-rg5g-v8jm)
- <https://github.com/TYPO3-CMS/core/commit/ac0565b7a539398a07adf21f04f85cd2574817d2>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2019-05-07-5.yaml>
- <https://github.com/TYPO3-CMS/core>
- <https://typo3.org/security/advisory/typo3-core-sa-2019-010>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-wj85-rg5g-v8jm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wj85-rg5g-v8jm/>. Everything for agents: <https://agentprime.io/llms.txt>.