Skip to content
eastbaycyber

CVE-2026-9559: Critical Mautic 7 Path Traversal

CVSS · Critical
9.9
In CISA KEV
No
Published
Nov 18
Patch SLA & TriageVector: Network
24 to 48 hours

Critical CVSS (9.9) reachable over network.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 9.9
Decode Vector & Sub-Scores →
CVE explainers 10 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-18
▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-9559 is a critical path-traversal flaw in Mautic 7 campaign-import ZIP extraction. - An authenticated user with campaign:imports:create may write PHP files outside the intended temporary directory. - No public PoC or CISA KEV listing was identified; restrict privileges and upgrade to the vendor-fixed Mautic 7 release.

CVE-2026-9559 is a critical Mautic 7 vulnerability affecting campaign-import ZIP extraction. A suitably privileged, authenticated user may exploit crafted archive paths to write PHP files or overwrite sensitive application files outside the intended extraction directory. The issue can potentially lead to remote code execution under the web-server account.

Vulnerability at a Glance

Field Details
CVE CVE-2026-9559
Product Mautic 7
CVSS 9.9 Critical
Attack vector Network-based campaign-import functionality
Authentication Required
Privileges required campaign:imports:create
Impact Arbitrary file write and potential remote code execution
Patch available Yes; confirm the exact fixed version in the vendor advisory
CISA KEV status Not listed at the time of lookup
Public PoC None identified in the supplied research

CVE-2026-9559 affects Mautic’s campaign-import workflow, specifically the handling of uploaded ZIP archives. The vulnerability allows a suitably authorized user to write PHP files or overwrite sensitive application files outside the intended extraction directory, rather than merely read application data.

The available records establish a critical CVSS score but do not include the exact CVSS vector string. Confirm the vector in the current NVD record before using it for formal risk calculations or compliance reporting. The NVD record also identifies Mautic 7 as affected without publishing a precise lower and upper version range.

Analyst’s Take: The required permission limits the immediate attacker pool, but the impact remains substantial because a successful import can place executable PHP outside the intended directory. Treat privilege review and patch verification as linked tasks: reducing access helps contain exposure, while only the vendor fix addresses the extraction flaw.

What Is This Vulnerability?

The flaw is a path-traversal vulnerability in the validation logic used when Mautic extracts campaign-import ZIP files. Archive entries can contain paths designed to move upward from the temporary extraction directory, such as paths using parent-directory components. If the application validates the archive name without reliably normalizing and constraining the final destination, an extracted file can escape the directory intended by the import process.

An authenticated user with the campaign:imports:create permission may submit a crafted archive. The resulting write operation can place a PHP file in a web-accessible or executable location, or overwrite internal configuration and cache components. Depending on the deployment layout and web-server permissions, this can lead to remote code execution as the web-server account.

The reported impact extends beyond a file-management defect. Successful exploitation could allow modification of application behavior, theft of credentials and API tokens, persistence in the webroot, or further compromise of the host. Exploitation still depends on authentication and the relevant Mautic permission; this is not described as an unauthenticated Internet-wide attack.

Technical Notes

The security boundary that must hold during extraction is:

resolved_extraction_path(entry) must remain inside designated_temp_directory

A secure implementation normally canonicalizes the destination path, rejects traversal and unsafe link behavior, and verifies that the resolved path remains beneath the extraction root before writing. The supplied research indicates that the vendor fix introduces strict path normalization and validation to keep archive entries confined to the designated temporary directory.

Defenders should not attempt to reproduce the issue against production systems. If testing is required, use an isolated clone with synthetic data and no network access. Preserve the original archive and relevant logs as evidence rather than repeatedly uploading suspicious files to a live installation.

For broader context on vulnerability response processes, see Linux patch management best practices.

AnalystImpact · assess the risk

Who Is Affected?

The affected product is Mautic 7. The available NVD data identifies the major release but does not provide a precise lower or upper version boundary. Administrators should therefore treat all Mautic 7 installations as potentially affected until the vendor advisory confirms the exact vulnerable and fixed releases.

The relevant exposure is not limited to installations that actively use campaign imports every day. Any deployment that exposes the campaign-import feature to a user holding campaign:imports:create should be assessed. Internet-facing Mautic instances, shared administrative environments, and installations with broad or reused roles deserve priority because a compromised account with this permission may provide the path to exploitation.

Deployment condition Assessment
Mautic 7 with campaign imports enabled Potentially affected
User or role with campaign:imports:create Exploitation prerequisite identified in the record
Mautic version outside major release 7 Not established as affected by the supplied record; verify with the vendor
Mautic 7 upgraded to the confirmed vendor-fixed release Expected to be remediated, subject to version verification
Unauthenticated public visitor Not identified as sufficient for exploitation

Removing public access alone does not resolve the risk. An attacker could first compromise or abuse an account, exploit excessive privileges, or use a legitimate internal account. Review role assignments and identity-provider logs alongside application exposure.

CVSS Score Breakdown

NVD assigns CVE-2026-9559 a CVSS base score of 9.9 Critical. The score indicates a potentially severe compromise path, particularly because exploitation may result in arbitrary PHP file writes and remote code execution. The supplied NVD API result did not expose the vector string, so the exact values for attack complexity, user interaction, scope, confidentiality, integrity, and availability must be confirmed directly in the NVD record.

Known characteristics can still inform operational prioritization. The attack is associated with a network-accessible application feature, requires authentication, and requires the specific campaign-import permission. Those requirements reduce the set of immediately eligible attackers compared with an unauthenticated vulnerability, but they do not make the issue low risk.

The impact side is especially important. Arbitrary writes into sensitive application locations can affect confidentiality and integrity, while code execution under the web-server identity may enable access to Mautic secrets, databases, operating-system resources, and connected services. A high score should accelerate remediation, but teams should avoid reconstructing an unofficial CVSS vector from incomplete data.

Technical Notes

For asset and vulnerability-management records, retain the confirmed score and mark the vector as pending verification rather than inventing a string:

CVE: CVE-2026-9559
CVSS: 9.9 Critical
CVSS vector: Confirm against current NVD record
Authentication: Required
Required permission: campaign:imports:create

Exploitation Status

CVE-2026-9559 was not listed in the CISA Known Exploited Vulnerabilities catalog at the time of the supplied lookup. CISA has not confirmed exploitation in the wild, and there are no CISA KEV dates, remediation deadlines, required-action text, or ransomware campaign designation for this CVE.

No public proof-of-concept repository or exploit code was identified in the supplied sources. The accurate status is therefore: public PoC not identified, and exploitation in the wild not confirmed. This status can change, particularly for a vulnerability that may enable authenticated remote code execution through a commonly deployed web application.

Absence from KEV is not evidence that exploitation is impossible or absent. Organizations should prioritize internet-facing Mautic systems and monitor for suspicious archive uploads, unexpected PHP files, privilege changes, and web requests to newly created files. Treat any evidence of unauthorized file creation as a potential compromise, not merely as an attempted upload.

ResponderRunbook · act now

How to Detect It

Detection should combine Mautic application telemetry, web-server access logs, filesystem monitoring, and identity events. The available research does not provide a vendor-specific log event or a definitive network signature, so defenders should build detections around campaign-import activity, archive uploads, path anomalies, and PHP files appearing in locations where they are not expected.

Start by identifying Mautic’s webroot, cache directories, temporary extraction directories, and configuration locations. Establish a baseline of legitimate PHP files and monitor for additions or modifications. Pay particular attention to files created shortly after a campaign-import request, files containing PHP in cache or upload directories, and writes performed by the web-server account.

Technical Notes

A basic Linux search for recently modified PHP files can support triage. Adjust paths to the local deployment and preserve results before deleting anything:

find /var/www/mautic \
  -type f -iname '*.php' \
  -mmin -1440 \
  -printf '%TY-%Tm-%TdT%TH:%TM:%TS %u %g %m %p\n' \
  2>/dev/null

A filesystem rule can alert when PHP files are created in temporary, cache, upload, or other non-code directories. With auditd, the following is a starting point; replace paths with the actual Mautic directories:

auditctl -w /var/www/mautic/var/cache -p wa -k mautic-cache-writes
auditctl -w /var/www/mautic/var/tmp -p wa -k mautic-temp-writes

Review events using:

ausearch -k mautic-cache-writes -i
ausearch -k mautic-temp-writes -i

A useful web-log hunting pattern is campaign-import activity followed by requests for a newly created PHP file:

same client or authenticated account
AND POST request to a Mautic campaign-import endpoint
AND subsequent GET/POST request for an unexpected *.php path
within 15 minutes

Example pseudocode for a SIEM query:

(event.category = "web"
 AND http.request.method = "POST"
 AND url.path contains "campaign")
AND
(event.category = "web"
 AND url.path endswith ".php")
AND
sequence by source.ip or user.id within 15m

The exact endpoint and log fields vary by Mautic version, routing configuration, and reverse proxy. Confirm the campaign-import route from application logs and your deployment rather than relying on a generic path match.

Mitigation and Patching

The vendor-advisory material indicates that a fix is available and adds strict path normalization plus validation that extracted entries remain within the designated temporary directory. However, the supplied NVD and advisory output did not expose a definitive fixed-version number. Do not publish or operationalize an unverified version claim. Consult the Mautic security advisory and its release metadata, then upgrade every affected Mautic 7 installation to the specific patched release identified there.

Until the fixed version is confirmed and deployed, remove campaign:imports:create from roles that do not require it. Restrict campaign-import access to a small set of trusted administrators, enforce multifactor authentication for those accounts, and place administrative functionality behind a controlled access layer where practical. These measures reduce exposure but do not replace the vendor fix.

If compromise is suspected, isolate the host or application tier, preserve logs and suspicious archives, and investigate the web-server account’s file writes. Review Mautic configuration for database credentials, SMTP credentials, API tokens, and other secrets. Rotate exposed credentials after containment and validate database and connected-service activity for unauthorized use.

For related security-monitoring guidance, see open-source SIEM alternatives.

Technical Notes

Because the exact fixed version is not available in the supplied record, first inspect the vendor advisory and repository metadata, then use the upgrade method appropriate to the installation. For a Composer-managed deployment, the operational pattern is:

# Run from the Mautic application directory.
composer show mautic/core
composer update mautic/core --with-all-dependencies
php bin/console cache:clear --no-warmup

Use the vendor’s documented package constraint and release-specific upgrade procedure rather than blindly running an unconstrained update. Before changing production, back up the database and application configuration, test the target release, and confirm that the installed version is the fixed release named by the Mautic advisory.

A temporary permission-reduction example for role configuration is:

Remove campaign:imports:create
from every role that does not explicitly require campaign imports.

Do not rely on filesystem permissions as the sole workaround. The web process may need to write to some application directories, and overly broad changes can break Mautic or create new security problems. Combine least-privilege role changes with network restrictions, monitoring, and prompt patching.

After upgrading, verify the deployed version, review the application and web-server logs for failed or suspicious import attempts, and compare the webroot and configuration directories against a known-good baseline. If unexpected PHP files are discovered, do not simply delete them before collecting timestamps, hashes, ownership, and relevant logs.

References

  1. NVD: CVE-2026-9559 — CVE description, severity, and current NVD metadata.
  2. Mautic GitHub Security Advisory: GHSA-6r9h-4h75-7q4x — Vendor advisory and remediation details, including the confirmed fixed release.
  3. CVE.org: CVE-2026-9559 — Official CVE record.
  4. CISA Known Exploited Vulnerabilities Catalog — Check current KEV status; the supplied lookup found no listing for CVE-2026-9559.

CVE-2026-9559 should be treated as a high-priority Mautic 7 remediation item despite the absence of a confirmed public PoC or CISA KEV listing. Start by verifying the vendor-fixed release and removing campaign:imports:create from unnecessary roles, then use the available logs and filesystem checks to determine whether suspicious imports or PHP writes have already occurred.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

Last verified: 2026-11-18

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.