# Typo3 Information Disclosure

Advisory record · `GHSA-vccp-5v5h-p8m6`

- **Identifiers:** `GHSA-vccp-5v5h-p8m6` · `CVE-2014-3946` · `PKSA-7k6t-m8n5-b4mf`
- **State:** Confirmed
- **Severity:** No CVSS score
- **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:** 17 May 2022
- **Updated:** 14 Apr 2025
- **Reviewed by a person:** No

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

## Affected packages

- `typo3/cms` (Packagist): affected `>=6.2.0, <6.2.3`; fixed in `6.2.3`

## Machine-written summary

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

> TYPO3 CMS (typo3/cms) versions 6.2.0 up to 6.2.3 are affected. The Extbase query cache, introduced in version 6.2, did not account for the user groups of logged-in users, so cached results meant for one user group could be shown to a different group, which leads to information disclosure. Upgrade to version 6.2.3 or later. The source gives few details about the exact conditions required to trigger it.

Written 3 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.011, the 66th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:27 UTC: First seen by agentprime
- 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vccp-5v5h-p8m6)

## Sources

- [GitHub Advisory Database: GHSA-vccp-5v5h-p8m6](https://github.com/advisories/GHSA-vccp-5v5h-p8m6)
- [OSV: GHSA-vccp-5v5h-p8m6](https://osv.dev/vulnerability/GHSA-vccp-5v5h-p8m6)
- <https://nvd.nist.gov/vuln/detail/CVE-2014-3946>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2014-3946.yaml>
- <https://github.com/TYPO3/typo3>
- <https://typo3.org/security/advisory/typo3-core-sa-2014-001>
- <https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2014-001>
- <http://www.debian.org/security/2014/dsa-2942>
- <http://www.openwall.com/lists/oss-security/2014/06/03/2>

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-vccp-5v5h-p8m6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vccp-5v5h-p8m6/>. Everything for agents: <https://agentprime.io/llms.txt>.
