# TYPO3 Security Misconfiguration in User Session Handling

Advisory record · `GHSA-xmgr-jff3-fcfv`

- **Identifiers:** `GHSA-xmgr-jff3-fcfv` · `PKSA-xy95-nkpr-w5rm`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-384](https://cwe.mitre.org/data/definitions/384.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 30 May 2024
- **Updated:** 5 Dec 2024
- **Reviewed by a person:** No

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

## Affected packages

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

## Machine-written summary

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

> TYPO3 CMS core (typo3/cms-core) versions 8.0.0 up to 8.7.25 and 9.0.0 up to 9.5.6 do not revoke existing sessions when a user changes their password. An attacker who already holds a valid backend or frontend user account can keep using sessions for that account after the password is changed. Upgrade to version 8.7.25 or 9.5.6, or later.

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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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-xmgr-jff3-fcfv)

## Sources

- [GitHub Advisory Database: GHSA-xmgr-jff3-fcfv](https://github.com/advisories/GHSA-xmgr-jff3-fcfv)
- [OSV: GHSA-xmgr-jff3-fcfv](https://osv.dev/vulnerability/GHSA-xmgr-jff3-fcfv)
- <https://github.com/TYPO3-CMS/core/commit/437bf78c0ef64a059c7feaa5164f6f028507b425>
- <https://github.com/TYPO3-CMS/core/commit/e21f0e5d29b68a7e64448762b3f86ac24d36627f>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2019-05-07-2.yaml>
- <https://github.com/TYPO3-CMS/core>
- <https://typo3.org/security/advisory/typo3-core-sa-2019-011>

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-xmgr-jff3-fcfv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xmgr-jff3-fcfv/>. Everything for agents: <https://agentprime.io/llms.txt>.
