# TYPO3 CMS has Broken Access Control in its Form Framework Advisory record · `GHSA-hwvq-2w67-rvxp` - **Identifiers:** `GHSA-hwvq-2w67-rvxp` · `CVE-2026-47346` · `PKSA-6jfs-jhtj-72x7` · `PKSA-m239-hcqk-kg59` - **State:** Confirmed - **Severity:** CVSS 7.6 High - **Critical:** No - **Weakness (CWE):** [CWE-178](https://cwe.mitre.org/data/definitions/178.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-178](https://agentprime.io/advisories/tag/cwe-178.md) - **Published:** 12 Jun 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 12 Jun 2026, 19:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `typo3/cms-core` (Packagist): affected `<10.4.57 || >=11.0.0, <11.5.51 || >=12.0.0, <12.4.46 || >=13.0.0, <13.4.31 || >=14.0.0, <14.3.3`; fixed in `10.4.57`, `11.5.51`, `12.4.46`, `13.4.31`, `14.3.3` - `typo3/cms-form` (Packagist): affected `<10.4.57 || >=11.0.0, <11.5.51 || >=12.0.0, <12.4.46 || >=13.0.0, <13.4.31 || >=14.0.0, <14.3.3`; fixed in `10.4.57`, `11.5.51`, `12.4.46`, `13.4.31`, `14.3.3` ## 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-form, in versions below 10.4.57, from 11.0.0 to below 11.5.51, from 12.0.0 to below 12.4.46, from 13.0.0 to below 13.4.31, and from 14.0.0 to below 14.3.3, contain a broken access control flaw in the Form Framework. A backend user with file write permissions can upload form definition files with mixed-case extensions to bypass the upload restriction, and a crafted file can then run arbitrary SQL to create administrative backend accounts. Upgrade to 10.4.57, 11.5.51, 12.4.46, 13.4.31, or 14.3.3 or later, depending on the installed release line. Written 31 Oct 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.6 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`, from CNA (TYPO3) - **CISA KEV:** Not listed. - **EPSS:** 0.0025, the 16th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:00 UTC: First seen by agentprime - 31 Oct 2026, 14:00 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hwvq-2w67-rvxp) ## Sources - [GitHub Advisory Database: GHSA-hwvq-2w67-rvxp](https://github.com/advisories/GHSA-hwvq-2w67-rvxp) - [OSV: GHSA-hwvq-2w67-rvxp](https://osv.dev/vulnerability/GHSA-hwvq-2w67-rvxp) - - - - - - - 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: .