GHSA-p4xx-m758-3hpx is a low-severity (CVSS 3.3) Server-Side Request Forgery (SSRF) vulnerability in typo3/cms-webhooks. A fix is available for typo3/cms-webhooks — see the affected versions and patch details below.
TYPO3 CMS Webhooks Server Side Request Forgery
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-p4xx-m758-3hpx.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-p4xx-m758-3hpx plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
typo3/cms-webhooks🐘typo3/cms-webhooksReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Problem
Webhooks are inherently vulnerable to Server-Side Request Forgery (SSRF), which can be exploited by adversaries to target internal resources (e.g., localhost or other services on the local network). While this is not a vulnerability in TYPO3 itself, it may enable attackers to blindly access systems that would otherwise be inaccessible. An administrator-level backend user account is required to exploit this vulnerability.
Solution
Update to TYPO3 versions 12.4.31 LTS, 13.4.12 LTS that fix the problem described.
[!IMPORTANT]
Manual actions required
To mitigate potential SSRF risks via webhooks, it is recommended to explicitly allow access only to trusted hosts. This can be achieved by configuring the allowlist in
$GLOBALS['TYPO3_CONF_VARS']['HTTP']['allowed_hosts']['webhooks'].If the allowlist is not defined or set to
null, all requests will be allowed. If the allowlist is an emptyarray, all requests will be blocked.By default, the factory setting allows all requests. This prevents existing webhooks from failing after upgrading to the affected TYPO3 versions. Administrators must configure this setting manually to enforce restrictions.
Credits
Thanks to the National Cyber Security Center (NCSC) of Switzerland for reporting this issue, and to TYPO3 core & security team member Benjamin Franzke for fixing it.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-webhooks | ≥ 12.0.0&&< 12.4.31 | 12.4.31composer require typo3/cms-webhooks:^12.4.31 |
| 🐘Packagist | typo3/cms-webhooks | ≥ 13.0.0&&< 13.4.12 | 13.4.12composer require typo3/cms-webhooks:^13.4.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-webhooks, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-webhooks to 12.4.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p4xx-m758-3hpx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p4xx-m758-3hpx can be triaged on real exposure rather than presence alone.
Tailored to GHSA-p4xx-m758-3hpx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p4xx-m758-3hpx in your dependencies?
O3 Security finds GHSA-p4xx-m758-3hpx across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.