# SQL Injection in TYPO3 Frontend Login

Advisory record · `GHSA-j86x-pjmr-9m6w`

- **Identifiers:** `GHSA-j86x-pjmr-9m6w` · `PKSA-83dv-xmw9-2793`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 5 Jun 2024
- **Updated:** 2 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Jun 2024, 14:23 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.26 || >=7.6.0, <7.6.10`; fixed in `6.2.26`, `7.6.10`

## Machine-written summary

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

> TYPO3 CMS versions from 6.2.0 before 6.2.26 and from 7.6.0 before 7.6.10 are affected by a SQL injection flaw in the frontend login component, caused by improperly escaped user input. An attacker needs a valid frontend user account to exploit it, and the source gives few details on what they could then read or change. Upgrade to version 6.2.26 or 7.6.10 or later.

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.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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-j86x-pjmr-9m6w)

## Sources

- [GitHub Advisory Database: GHSA-j86x-pjmr-9m6w](https://github.com/advisories/GHSA-j86x-pjmr-9m6w)
- [OSV: GHSA-j86x-pjmr-9m6w](https://osv.dev/vulnerability/GHSA-j86x-pjmr-9m6w)
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2016-07-19-3.yaml>
- <https://typo3.org/security/advisory/typo3-core-sa-2016-016>

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-j86x-pjmr-9m6w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j86x-pjmr-9m6w/>. Everything for agents: <https://agentprime.io/llms.txt>.
