# TYPO3 CMS Webhooks Server Side Request Forgery

Advisory record · `GHSA-p4xx-m758-3hpx`

- **Identifiers:** `GHSA-p4xx-m758-3hpx` · `CVE-2025-47936` · `PKSA-q52p-kj6f-r4yz`
- **State:** Confirmed
- **Severity:** CVSS 3.3 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 20 May 2025
- **Updated:** 20 May 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 May 2025, 19:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `typo3/cms-webhooks` (Packagist): affected `>=12.0.0, <12.4.31 || >=13.0.0, <13.4.12`; fixed in `12.4.31`, `13.4.12`

## Machine-written summary

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

> TYPO3 CMS Webhooks (typo3/cms-webhooks) versions 12.0.0 to before 12.4.31 and 13.0.0 to before 13.4.12 are vulnerable to server-side request forgery. An attacker with administrator-level backend access can make the server send requests to internal resources such as localhost or other systems on the local network. Upgrade to 12.4.31 or 13.4.12. As a workaround, set the allowlist at $GLOBALS\['TYPO3_CONF_VARS'\]\['HTTP'\]\['allowed_hosts'\]\['webhooks'\] to trusted hosts only, since the default allows all requests.

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

- 3.3 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 20th percentile, on 15 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-p4xx-m758-3hpx)

## Sources

- [GitHub Advisory Database: GHSA-p4xx-m758-3hpx](https://github.com/advisories/GHSA-p4xx-m758-3hpx)
- [OSV: GHSA-p4xx-m758-3hpx](https://osv.dev/vulnerability/GHSA-p4xx-m758-3hpx)
- <https://github.com/TYPO3/typo3/security/advisories/GHSA-p4xx-m758-3hpx>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-47936>
- <https://github.com/TYPO3-CMS/webhooks/commit/0df8b8adae577876fa253679c9ef3fe2a7ee64fd>
- <https://github.com/TYPO3-CMS/webhooks>
- <https://typo3.org/security/advisory/typo3-core-sa-2025-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-p4xx-m758-3hpx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p4xx-m758-3hpx/>. Everything for agents: <https://agentprime.io/llms.txt>.