# TYPO3 CMS vulnerable to Denial of Service in Page Error Handling

Advisory record · `GHSA-fffr-7x4x-f98q`

- **Identifiers:** `GHSA-fffr-7x4x-f98q` · `BIT-typo3-2022-36104` · `CVE-2022-36104` · `PKSA-h28q-88f6-24c1` · `PKSA-p25q-9h89-q9b8`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 16 Sept 2022
- **Updated:** 6 Dec 2023
- **Reviewed by a person:** No

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

## Affected packages

- `typo3/cms-core` (Packagist): affected `>=11.4.0, <11.5.16`; fixed in `11.5.16`
- `typo3/cms` (Packagist): affected `>=11.4.0, <11.5.16`; fixed in `11.5.16`

## Machine-written summary

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

> TYPO3 CMS core (typo3/cms-core and typo3/cms) versions 11.4.0 up to but not including 11.5.16 are affected. A remote, unauthenticated attacker who requests invalid or non-existing resources can trigger the page error handler to recurse, which may cause a denial of service until the web server's limits are exceeded. Upgrade to version 11.5.16.

Written 5 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.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:32 UTC: First seen by agentprime
- 31 Oct 2026, 14:32 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fffr-7x4x-f98q)

## Sources

- [GitHub Advisory Database: GHSA-fffr-7x4x-f98q](https://github.com/advisories/GHSA-fffr-7x4x-f98q)
- [OSV: GHSA-fffr-7x4x-f98q](https://osv.dev/vulnerability/GHSA-fffr-7x4x-f98q)
- <https://github.com/TYPO3/typo3/security/advisories/GHSA-fffr-7x4x-f98q>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-36104>
- <https://github.com/TYPO3/typo3/commit/179dd7cd78947081d573fee2050e197faa556f13>
- <https://github.com/TYPO3/typo3/commit/fc51ccbf2bb8a8c959aa74cbceca124971e6e7fd>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2022-36104.yaml>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-36104.yaml>
- <https://github.com/TYPO3/typo3>
- <https://typo3.org/security/advisory/typo3-core-sa-2022-006>

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

---

The web page: <https://agentprime.io/advisories/GHSA-fffr-7x4x-f98q/>. Everything for agents: <https://agentprime.io/llms.txt>.
