# TYPO3 Disclosure of Information about Installed Extensions

Advisory record · `GHSA-p2h4-7fp3-cmh8`

- **Identifiers:** `GHSA-p2h4-7fp3-cmh8` · `PKSA-t2bp-d8b3-sc74`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.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:13 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.23 || >=9.0.0, <9.5.4`; fixed in `8.7.23`, `9.5.4`

## 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 to before 8.7.23 and 9.0.0 to before 9.5.4 are affected. The RequireJS package loading configuration can be abused to retrieve information about installed system and third-party extensions; the source does not state what access an attacker needs. Upgrade to version 8.7.23 or 9.5.4 to fix the issue.

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-p2h4-7fp3-cmh8)

## Sources

- [GitHub Advisory Database: GHSA-p2h4-7fp3-cmh8](https://github.com/advisories/GHSA-p2h4-7fp3-cmh8)
- [OSV: GHSA-p2h4-7fp3-cmh8](https://osv.dev/vulnerability/GHSA-p2h4-7fp3-cmh8)
- <https://github.com/TYPO3-CMS/core/commit/7960334bba1223a681283158f67a999334e88cf1>
- <https://github.com/TYPO3-CMS/core/commit/9453d8a8763fffa76deb6a16f6b99c0ab6f3d8f1>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2019-01-22-1.yaml>
- <https://typo3.org/security/advisory/typo3-core-sa-2019-001>

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

---

The web page: <https://agentprime.io/advisories/GHSA-p2h4-7fp3-cmh8/>. Everything for agents: <https://agentprime.io/llms.txt>.
