---
id: CVE-2026-115193
title: >-
  A stored Cross-Site Scripting (XSS) vulnerability exists in the contact detail
  view of Mautic 7
summary: >-
  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 fi…
severity: high
cvss: 8.2
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N'
cvssSource: cna
cwe:
  - CWE-79
product: mautic/core
affected:
  - mautic/core >= 7.0.0 < 7.2.2
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-10-26T14:58:46.837321Z'
published: '2026-10-26'
updated: '2026-10-26'
sourceUpdated: '2026-10-26T15:35:53.085Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-115193'
references:
  - url: 'https://github.com/mautic/mautic/security/advisories/GHSA-3295-vq3p-93rw'
tags:
  - cve.org
ingestedAt: '2026-10-26T14:27:31.837Z'
---

## Overview

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.

## Affected

- `mautic/core >= 7.0.0 < 7.2.2`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

### Workarounds

There are no official workarounds. To mitigate this vulnerability without upgrading, restrict contact create and edit permissions and API access to trusted users, and avoid mapping public form fields or publicly updatable settings to HTML-type contact fields.