# CVE-2026-115188: An unrestricted file upload vulnerability exists in the campaign import feature of Mautic 7.


- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-mxjf-pghx-h299

## What is CVE-2026-115188?

CVE-2026-115188 is a critical vulnerability, published on 26 Oct 2026. 

### Official description

An unrestricted file upload vulnerability exists in the campaign import feature of Mautic 7. When processing an uploaded campaign archive, the application copies the bundled asset files into a publicly accessible media directory without restricting their file names or types. An authenticated user with permission to create campaign imports can exploit this through the user interface or the API (/api/campaigns/import) to place arbitrary files, including server-side scripts, in the web root. Administrator privileges are not required. On web servers that honor per-directory configuration, such as the default Apache setup of the official Mautic Docker image, this leads to remote code execution with the privileges of the web server user, including access to the Mautic configuration, application secrets, and contact data.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-115188?


## How do I fix CVE-2026-115188?

No fix has been published for CVE-2026-115188 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115188 being exploited?

There is no known exploitation of CVE-2026-115188 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115188 and fix it if it is affected.

What it is: CVE-2026-115188 is a critical vulnerability, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115188 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115188/ (Markdown: https://insights.sbomify.com/CVE-2026-115188/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115188
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115188
- OSV: https://osv.dev/vulnerability/CVE-2026-115188

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115188/
Summaries are generated and may contain mistakes; the official description above is the record.