Mautic Focus component Vulnerable to SSRFGHSA-jmv8-8j9j-rcpc
MEDIUMGHSA-jmv8-8j9j-rcpc is a medium-severity (CVSS 6.4) Server-Side Request Forgery (SSRF) vulnerability in mautic/core. A fix is available for mautic/core — see the affected versions and patch details below.
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-jmv8-8j9j-rcpc.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-jmv8-8j9j-rcpc by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
mautic/core🐘mautic/core🐘mautic/core🐘mautic/coreReal-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
Summary
A Server-Side Request Forgery (SSRF) vulnerability exists in the Mautic Focus component (MauticFocusBundle). Under certain conditions, insufficiency in validating user-supplied URLs allows authenticated users to trigger outbound HTTP requests from the hosting server.
Impact
An authenticated user with access to the Mautic panel can exploit this vulnerability to perform internal port probing or force the server to initiate requests to external or arbitrary internal destinations. This can enable internal network reconnaissance or mapping of firewalled infrastructure.
Patched Versions
This security issue has been fixed in the following releases:
- 7.1.2
- 6.0.9
- 5.2.11
- 4.4.20 ELTS
Mautic strongly recommend upgrading to the latest version corresponding to your release branch.
Workarounds
There are no official workarounds. To completely mitigate the exposure without upgrading, disabling or limiting external network access from the Mautic web server to internal-only subnets/local hosts is recommended.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | mautic/core | ≥ 4.0.0 | No fix |
| 🐘Packagist | mautic/core | ≥ 5.0.0&&< 5.2.11 | 5.2.11composer require mautic/core:^5.2.11 |
| 🐘Packagist | mautic/core | ≥ 6.0.0&&< 6.0.9 | 6.0.9composer require mautic/core:^6.0.9 |
| 🐘Packagist | mautic/core | ≥ 7.0.0&&< 7.1.2 | 7.1.2composer require mautic/core:^7.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mautic/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of mautic/core has shipped for GHSA-jmv8-8j9j-rcpc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is GHSA-jmv8-8j9j-rcpc in your dependencies?
Find it across Packagist, including transitive dependencies.