GHSA-jmv8-8j9j-rcpc
MEDIUMMautic Focus component Vulnerable to SSRF
Blast Radius
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.11 |
| 🐘Packagist | mautic/core | ≥ 6.0.0&&< 6.0.9 | 6.0.9 |
| 🐘Packagist | mautic/core | ≥ 7.0.0&&< 7.1.2 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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 pinpoints whether GHSA-jmv8-8j9j-rcpc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-jmv8-8j9j-rcpc. 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-jmv8-8j9j-rcpc in your dependencies?
O3 detects GHSA-jmv8-8j9j-rcpc across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.