# TYPO3 Security Misconfiguration in Frontend Session Handling

Advisory record · `GHSA-82vp-jr39-4j2j`

- **Identifiers:** `GHSA-82vp-jr39-4j2j` · `PKSA-kgft-67y3-84tv`
- **State:** Confirmed
- **Severity:** CVSS 8.2 High
- **Critical:** No
- **Weakness (CWE):** [CWE-488](https://cwe.mitre.org/data/definitions/488.html)
- **Tags:** [CWE-488](https://agentprime.io/advisories/tag/cwe-488.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:22 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.27 || >=9.0.0, <9.5.8`; fixed in `8.7.27`, `9.5.8`

## Machine-written summary

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

> TYPO3 typo3/cms-core versions 8.0.0 up to 8.7.27 and 9.0.0 up to 9.5.8 are affected. During logout, frontend user session data is kept and turned into an anonymous session, so a later user of the same client application can access the previous user's session data. Upgrade to 8.7.27, 9.5.8, or later fixed versions. The source gives few further details.

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

- 8.2 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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-82vp-jr39-4j2j)

## Sources

- [GitHub Advisory Database: GHSA-82vp-jr39-4j2j](https://github.com/advisories/GHSA-82vp-jr39-4j2j)
- [OSV: GHSA-82vp-jr39-4j2j](https://osv.dev/vulnerability/GHSA-82vp-jr39-4j2j)
- <https://github.com/TYPO3-CMS/core/commit/c8c08ca0c26db02753c243e175a8a045628341b6>
- <https://github.com/TYPO3-CMS/core/commit/fe43834075ae283c8cd91949e9f1dfd18b2d492f>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2019-06-25-3.yaml>
- <https://github.com/TYPO3-CMS/core>
- <https://typo3.org/security/advisory/typo3-core-sa-2019-018>

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-82vp-jr39-4j2j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-82vp-jr39-4j2j/>. Everything for agents: <https://agentprime.io/llms.txt>.