← Back
CVE-2026-9557
medium
CVSS 6.4
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**SSRF** (CWE-918) exists in mautic/core. Attackers reach the vulnerable code path via ``MauticFocusBundle`` without authentication.
📍 Affected scope
mautic/core — . Attack surface: `MauticFocusBundle`.
🔥 Severity
Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.1.2**.
🛡️ Workaround
Workaround: There are no official workarounds.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There are no official workarounds.パッチが適用されるまでの応急処置として、There are no official workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade mautic/core to 7.1.2ステージング環境で 7.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
mautic/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.2"}]}]