# TYPO3 Security Misconfiguration in Install Tool Cookie

Advisory record · `GHSA-f777-f784-36gm`

- **Identifiers:** `GHSA-f777-f784-36gm` · `PKSA-b9qm-1gk1-gg53`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-1004](https://cwe.mitre.org/data/definitions/1004.html)
- **Tags:** [CWE-1004](https://agentprime.io/advisories/tag/cwe-1004.md)
- **Published:** 7 Jun 2024
- **Updated:** 4 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Jun 2024, 19:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `typo3/cms` (Packagist): affected `>=7.0.0, <7.6.32 || >=8.0.0, <8.7.21 || >=9.0.0, <9.5.2`; fixed in `7.6.32`, `8.7.21`, `9.5.2`

## Machine-written summary

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

> TYPO3 (typo3/cms) versions 7.0.0 up to 7.6.32, 8.0.0 up to 8.7.21, and 9.0.0 up to 9.5.2 are affected. Cookies set by the Install Tool are not restricted to HTTP-only, so when combined with another flaw such as cross-site scripting, an attacker could hijack an active Install Tool session. Upgrade to 7.6.32, 8.7.21, or 9.5.2, depending on your branch.

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.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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-f777-f784-36gm)

## Sources

- [GitHub Advisory Database: GHSA-f777-f784-36gm](https://github.com/advisories/GHSA-f777-f784-36gm)
- [OSV: GHSA-f777-f784-36gm](https://osv.dev/vulnerability/GHSA-f777-f784-36gm)
- <https://github.com/TYPO3/typo3/commit/13328b0f74ac589a20b021db814dfa672581c26a>
- <https://github.com/TYPO3/typo3/commit/918e50e4d20d88c7e40ad3bb134267d07706b0b1>
- <https://github.com/TYPO3/typo3/commit/a5359491e3fb3164a6ba96a66c8e67fbb9971a4c>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2018-12-11-4.yaml>
- <https://github.com/TYPO3/typo3>
- <https://typo3.org/security/advisory/typo3-core-sa-2018-009>

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-f777-f784-36gm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f777-f784-36gm/>. Everything for agents: <https://agentprime.io/llms.txt>.