# TYPO3 Denial of Service in Frontend Record Registration

Advisory record · `GHSA-hjx5-v9xg-7h25`

- **Identifiers:** `GHSA-hjx5-v9xg-7h25` · `PKSA-jktp-yswk-rrww`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **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:** 30 May 2024
- **Updated:** 5 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 May 2024, 15:36 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.21 || >=7.0.0, <7.6.32`; fixed in `8.7.21`, `7.6.32`

## Machine-written summary

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

> TYPO3 typo3/cms-core versions >=7.0.0 and <7.6.32, and >=8.0.0 and <8.7.21, are affected. An unauthenticated attacker can use the frontend record registration feature (the basic shopping cart, driven by recs URL parameters) to create an unlimited number of session-data records in the database, causing denial of service. Upgrade to typo3/cms-core 7.6.32 or 8.7.21.

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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, 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-hjx5-v9xg-7h25)

## Sources

- [GitHub Advisory Database: GHSA-hjx5-v9xg-7h25](https://github.com/advisories/GHSA-hjx5-v9xg-7h25)
- [OSV: GHSA-hjx5-v9xg-7h25](https://osv.dev/vulnerability/GHSA-hjx5-v9xg-7h25)
- <https://github.com/TYPO3-CMS/core/commit/5a44f93e9233e8f72159f9a67db26ed4bd5a10e0>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2018-12-11-7.yaml>
- <https://github.com/TYPO3-CMS/core>
- <https://typo3.org/security/advisory/typo3-core-sa-2018-012>

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

---

The web page: <https://agentprime.io/advisories/GHSA-hjx5-v9xg-7h25/>. Everything for agents: <https://agentprime.io/llms.txt>.
