# CVE-2026-115193: A stored Cross-Site Scripting (XSS) vulnerability exists in the contact detail view of Mautic 7.


- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-3295-vq3p-93rw

## What is CVE-2026-115193?

CVE-2026-115193 is a high-severity vulnerability, published on 26 Oct 2026. 

### Official description

A stored Cross-Site Scripting (XSS) vulnerability exists in the contact detail view of Mautic 7. Values of HTML-type custom contact fields are rendered without output sanitization. A user or integration able to write a value to such a field (for example, through contact editing, the contact API, or a form submission mapped to the field) can store a script payload in it. When another user, including an administrator, opens the affected contact's detail page, the injected script executes within the context of their active browser session. This could allow an attacker to perform administrative actions on behalf of the victim, such as creating new administrator accounts, altering system configuration, or accessing contact and campaign data.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-115193 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115193 is a high-severity vulnerability, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115193 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-115193/ (Markdown: https://insights.sbomify.com/CVE-2026-115193/index.md)
```

## Sources

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

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