SSRF (Server-Side Request Forgery) in mautic/core (CVE-2026-9557)
Summary
SSRF in mautic/core (CVE-2026-9557). Risk of unauthorized operations or information disclosure. Exploitable via MauticFocusBundle. Mitigation: upgrade to 7.1.2 or later.
Original description
The description as published by the source.
A Server-Side Request Forgery (SSRF) vulnerability exists in Mautic's Focus component. Due to insufficient validation of user-supplied URLs, an authenticated user can trigger outbound HTTP requests from the hosting server, enabling internal network reconnaissance or forcing requests to arbitrary internal or external destinations.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9557 has been found in mautic/core.
Attackers can target a specific entry point like MauticFocusBundle over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: upgrade mautic/core to 7.1.2 or later.
If unsure, ask your IT team or search "mautic/core CVE-2026-9557" on the vendor's site.
CVE-2026-9557 (mautic/core) — CWE-918 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: MauticFocusBundle
Patched: 7.1.2 — apply immediately
Workaround: There are no official workarounds.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in mautic/core. Attackers reach the vulnerable code path via MauticFocusBundle.
Check the vendor advisory for the affected versions of mautic/core. Attack surface: MauticFocusBundle.
Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.
Update to 7.1.2.
Workaround: There are no official workarounds.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mautic/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mautic/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mautic/coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There are no official workarounds.パッチが適用されるまでの応急処置として、There are no official workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade mautic/core to 7.1.2ステージング環境で 7.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web packagist.org