A Risk Model for Mautic Campaign Imports After CVE-2026-115188
CVE-2026-115188 is best understood as a chain of conditions. Mautic 7.0.0 through 7.2.1 accepts a campaign archive, copies its assets into media/, and fails to restrict their names or types. An authenticated identity with campaign import creation permission can supply the archive through the interface or /api/campaigns/import. The final impact depends on whether the web server executes the resulting file.
The vendor rates the vulnerability 9.9 Critical. The CVSS vector describes network reachability, low privileges, no user interaction, a scope change, and high impact across confidentiality, integrity, and availability. The advisory maps the issue to unrestricted file upload and does not require an administrator account. Mautic 7.2.2 is the fixed release.
Five conditions that drive risk
The first condition is version exposure. A Mautic 7 instance before 7.2.2 is affected. The second is identity reachability: a person or integration must be able to authenticate and create a campaign import. The third is endpoint reachability. The interface and API need to be accessible to that identity, even if the access is limited by network controls.
The fourth condition is whether the media directory can execute scripts. The advisory identifies the default Apache setup in the official Docker image as one such case. A host that serves files as inert data still faces an arbitrary-file-write problem but may avoid direct code execution. The fifth condition is the privilege and secret reachability of the web-server user, which shapes the impact after execution.
This model avoids treating every affected installation as equally exposed. It also avoids treating a low CVSS privilege requirement as low risk. The permission is ordinary enough for campaign work, and the outcome can cross into the host and application data.
Use exposure evidence carefully
ZoomEye Search app="Mautic" returned 19,775 product-fingerprint matches during this review. That number describes Mautic assets with the selected fingerprint; it does not prove which ones run a vulnerable version, permit campaign imports, or execute scripts in the media directory. The separate vul.cve="CVE-2026-115188" Filter returned zero. Product exposure and confirmed vulnerability are different measurements.
Use the observation to prioritize discovery, not to construct a victim count. An internal asset inventory should add application version, exposure to the import endpoint, identity permissions, web-server handler policy, and the ability of the web-server user to read secrets. These facts turn a broad internet count into a defensible organizational decision.
Prioritize by consequence
The highest-priority cases combine an affected version, a broadly reachable import endpoint, a large set of accounts with import permission, and a web server that executes media files. A host with the same version but no execution path still needs patching and evidence review, but its immediate code-execution risk is different.
Review service accounts separately from human users. An API credential may have broad access with little monitoring, and an account shared by an integration can hide who submitted an archive. Restrict unused endpoints, reduce permission assignments, and verify the effective web-server policy at the virtual-host level.
Detection changes the decision
An import event alone is not proof of exploitation. A new media file alone is not proof of execution. Correlate the authenticated request, archive processing, file creation, later file access, and process activity. Preserve logs and file hashes before cleanup. The distinction between attempted access, file write, and confirmed execution determines whether the response is a patch task or an incident.
Detection also needs a baseline. Know which accounts normally use campaign imports, which file types are expected in media, and which hosts can reach the endpoint. Without that context, a rare alert may be missed because the team has no approved example to compare against.
Remediate the chain
Upgrade to Mautic 7.2.2. Remove campaign import permission where it is not needed and restrict the remaining identities. Deny script execution under media/ at the server or virtual-host level. Limit endpoint reachability and review secrets available to the web-server user. The advisory lists no official workaround, so controls before the patch are temporary risk reduction.
After remediation, keep the risk model as a review tool. Recheck version distribution, permission changes, endpoint routes, handler policy, and historical evidence. CVE-2026-115188 is closed by the fixed release, but the conditions that made the upload valuable can recur in another feature or integration.
Top comments (0)