# TYPO3 Cross-Site Request Forgery in Backend User Module Advisory record · `GHSA-6w4x-gcx3-8p7v` - **Identifiers:** `GHSA-6w4x-gcx3-8p7v` · `CVE-2024-55894` · `PKSA-v3gm-s5dn-x7cy` - **State:** Confirmed - **Severity:** CVSS 4.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html) · [CWE-749](https://cwe.mitre.org/data/definitions/749.html) - **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md) · [CWE-749](https://agentprime.io/advisories/tag/cwe-749.md) - **Published:** 14 Jan 2025 - **Updated:** 20 May 2025 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 14 Jan 2025, 15:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `typo3/cms-beuser` (Packagist): affected `>=10.0.0, <10.4.48 || >=11.0.0, <11.5.42 || >=12.0.0, <12.4.25 || >=13.0.0, <13.4.3`; fixed in `10.4.48`, `11.5.42`, `12.4.25`, `13.4.3` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > TYPO3's backend user module (typo3/cms-beuser) is affected in versions 10.0.0 up to 10.4.48, 11.0.0 up to 11.5.42, 12.0.0 up to 12.4.25, and 13.0.0 up to 13.4.3. An attacker can use cross-site request forgery through deep links, for example by getting a logged-in backend user to open a malicious link, to trigger password resets for other backend users or end their sessions. Upgrade to 10.4.48, 11.5.42, 12.4.25, or 13.4.3, matching your release line. 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 - 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`, from CNA (GitHub_M) - **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:27 UTC: First seen by agentprime - 31 Oct 2026, 14:27 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6w4x-gcx3-8p7v) ## Sources - [GitHub Advisory Database: GHSA-6w4x-gcx3-8p7v](https://github.com/advisories/GHSA-6w4x-gcx3-8p7v) - [OSV: GHSA-6w4x-gcx3-8p7v](https://osv.dev/vulnerability/GHSA-6w4x-gcx3-8p7v) - - - - - - - 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: .