# TYPO3 leaks a hash secret in an error message

Advisory record · `GHSA-c22j-84c7-cm77`

- **Identifiers:** `GHSA-c22j-84c7-cm77` · `CVE-2009-0815` · `PKSA-bk4n-5q3v-pw9b`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-209](https://cwe.mitre.org/data/definitions/209.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 2 May 2022
- **Updated:** 10 Apr 2025
- **Reviewed by a person:** No

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

## Affected packages

- `typo3/cms` (Packagist): affected `>=3.3, <4.0.12 || >=4.1, <4.1.10 || >=4.2, <4.2.6`; fixed in `4.0.12`, `4.1.10`, `4.2.6`

## Machine-written summary

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

> TYPO3 (typo3/cms) 3.3 and later, before 4.0.12, 4.1.10, and 4.2.6, leaks a hash secret in an error message from the jumpUrl mechanism. A remote attacker who can make requests can use the leaked hash to read arbitrary files. Upgrade to 4.0.12, 4.1.10, or 4.2.6, matching your release branch.

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

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.42, the 98th 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-c22j-84c7-cm77)

## Sources

- [GitHub Advisory Database: GHSA-c22j-84c7-cm77](https://github.com/advisories/GHSA-c22j-84c7-cm77)
- [OSV: GHSA-c22j-84c7-cm77](https://osv.dev/vulnerability/GHSA-c22j-84c7-cm77)
- <https://nvd.nist.gov/vuln/detail/CVE-2009-0815>
- <https://github.com/TYPO3/typo3>
- <https://web.archive.org/web/20091206080208/http://typo3.org/teams/security/security-bulletins/typo3-sa-2009-002>
- <https://web.archive.org/web/20200915000000*/http://www.securitytracker.com/id?1021710>
- <http://www.debian.org/security/2009/dsa-1720>
- <http://www.openwall.com/lists/oss-security/2009/02/10/6>

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-c22j-84c7-cm77>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c22j-84c7-cm77/>. Everything for agents: <https://agentprime.io/llms.txt>.
