CVE-2026-9557
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA Server-Side Request Forgery (SSRF) vulnerability in Mautic's Focus component allows authenticated users to supply arbitrary URLs that the hosting server will request, enabling internal network reconnaissance and potential attacks against internal services or external targets.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Mautic installation versionCheck the version file in your Mautic installation (usually in app/appConstants.php or a version.json file in the root directory)Affected if The installed version falls within the affected version range for this CVE (check Mautic security advisories for the specific vulnerable versions)
-
Verify Focus component is enabledLog into Mautic admin panel and navigate to the Focus section (usually found under Channels or as a separate menu item), or check the database table for active focus itemsAffected if The Focus component is installed and accessible to authenticated users
-
Inspect Focus widget/element configurationIn Mautic admin, create or edit a Focus item and examine the available options for URL fields or webhooks; check if there are any fields accepting user-supplied URLs (such as redirect URLs, tracking URLs, or external resource URLs)Affected if There are configuration options that accept arbitrary URLs without visible validation
-
Test URL validation behavior (if authorized)Using an authenticated test account, attempt to supply an internal URL (such as http://localhost or http://127.0.0.1) in the Focus component URL fields to see if the application accepts and processes itAffected if The application accepts internal or arbitrary external URLs without rejecting them or requiring explicit allowlisting
-
Check for existing URL validation in Mautic configurationExamine Mautic configuration files (parameters.yml or app/config/local.php) for any URL validation or allowlist settings related to the Focus componentAffected if No URL validation or allowlisting is configured for the Focus component
Your environment is affected if you are running a vulnerable Mautic version with the Focus component enabled and accessible to authenticated users without proper URL validation in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict URL validation with domain/IP allowlisting for the Focus component to restrict outbound requests to approved targets only, and consider disabling or limiting the outbound request feature for lower-privileged users.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9557 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9557 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data