CVE-2026-9559
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 path traversal vulnerability exists in the campaign import feature of Mautic 7. When extracting uploaded ZIP files during campaign imports, a flaw in the validation logic allows file paths to escape the intended temporary directories. An authenticated user with campaign import privileges (campaign:imports:create) can write arbitrary PHP files to sensitive system directories. An attacker can exploit this to overwrite critical internal configuration or cache components, resulting in Remote Code Execution (RCE) under the context of the web server user.
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 confidenceMautic 7 contains a path traversal vulnerability in the campaign import feature where ZIP file extraction lacks proper path validation. An authenticated user with campaign:imports:create privileges can craft ZIP archives containing paths that escape the intended temporary directories, allowing arbitrary PHP files to be written to sensitive system locations. This enables attackers to overwrite configuration or cache files to achieve remote code execution as the web server user.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 and versionCheck the version file or admin dashboard for the installed Mautic version. Common locations include a version.php file in the root directory or the Updates & Support section in the admin panel.Affected if Running Mautic version 7.x without the CVE-2026-9559 patch applied
-
Verify campaign import feature is accessibleLog into Mautic as an administrator and navigate to the campaigns section to confirm the campaign import functionality exists and is accessible.Affected if The campaign import feature (campaign:imports:create) is available to the user account
-
Check for users with campaign:imports:create privilegeIn the Mautic admin panel, go to Users > Roles and Permissions. Review which roles or users have the 'campaign:imports:create' permission enabled.Affected if Any user account has the campaign:imports:create permission granted through their role
-
Inspect temporary directory configurationExamine the Mautic configuration files (typically in app/config or config directories) for paths related to temporary file storage, import processing, and ZIP extraction locations.Affected if The temporary directory is not explicitly set to a non-public location or lacks strict write restrictions
-
Review web server user permissionsCheck the filesystem permissions on Mautic directories, particularly the temporary/import folders and any writable system directories accessible to the web server user.Affected if The web server process has write access to system directories outside of the intended temporary folder
A user is affected if they are running an unpatched Mautic 7 installation where the campaign import feature is accessible and a user with campaign:imports:create privileges exists, combined with writable temporary directories that can be escaped via path traversal.
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 dataApply vendor-supplied patch for CVE-2026-9559 to fix the path validation logic in the campaign import ZIP extraction. Until patched, restrict or disable the campaign:imports:create permission for untrusted users.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9559 — 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-9559 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