# Backend Same-Site Request Forgery in TYPO3 CMS Advisory record · `GHSA-pqg8-crx9-g8m4` - **Identifiers:** `GHSA-pqg8-crx9-g8m4` · `BIT-typo3-2020-11069` · `CVE-2020-11069` · `PKSA-ttpr-h5zy-14x1` · `PKSA-vncq-mbcp-6vyd` - **State:** Confirmed - **Severity:** CVSS 8.0 High - **Critical:** No - **Weakness (CWE):** [CWE-346](https://cwe.mitre.org/data/definitions/346.html) · [CWE-352](https://cwe.mitre.org/data/definitions/352.html) - **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md) · [CWE-346](https://agentprime.io/advisories/tag/cwe-346.md) - **Published:** 13 May 2020 - **Updated:** 8 Jul 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 13 May 2020, 23:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `typo3/cms-core` (Packagist): affected `>=9.0.0, <9.5.17 || >=10.0.0, <10.4.2`; fixed in `9.5.17`, `10.4.2` - `typo3/cms` (Packagist): affected `>=10.0.0, <10.4.2 || >=9.0.0, <9.5.17`; fixed in `10.4.2`, `9.5.17` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > TYPO3 CMS packages typo3/cms-core and typo3/cms, versions from 9.0.0 before 9.5.17 and from 10.0.0 before 10.4.2, are vulnerable to same-origin request forgery in the backend and install tool. An attacker who has uploaded a malicious file to the web server, or who can supply HTML through a third-party extension, can trick a logged-in backend or install tool user into executing it, which may create new admin users. Upgrade to typo3/cms-core or typo3/cms 9.5.17 or 10.4.2. As a further measure, disallow direct script execution for /fileadmin/ and /uploads/ via Content Security Policy. 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 - 8.0 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0074, the 55th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:25 UTC: First seen by agentprime - 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pqg8-crx9-g8m4) ## Sources - [GitHub Advisory Database: GHSA-pqg8-crx9-g8m4](https://github.com/advisories/GHSA-pqg8-crx9-g8m4) - [OSV: GHSA-pqg8-crx9-g8m4](https://osv.dev/vulnerability/GHSA-pqg8-crx9-g8m4) - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .