---
id: "CVE-2026-115190"
kind: "vulnerability"
aliases: ["CVE-2026-115190"]
title: "Mautic: stored segment and custom field values enable PHP object injection"
severity: "high"
cvss: 8.0
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "mautic/core", "fixed": ["5.2.12", "6.0.10", "7.2.0"], "affected": ">= 2.15.2, < 5.2.12; >= 6.0.0, < 6.0.10; >= 7.0.0, < 7.2.0", "ecosystem": "packagist"}]
ecosystems: []
tags: ["cwe-502", "deserialization", "mautic", "package", "php", "self-hosted"]
not_affected_if: ["managed-hosting", "no-untrusted-segment-editors", "patched-5.2.12-6.0.10-7.2.0"]
published_at: "2026-10-26T14:16:30+00:00"
first_seen_at: "2026-10-26T14:30:36+00:00"
updated_at: "2026-10-26T14:32:58+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-115190", "first_seen_at": "2026-10-26T14:30:36+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-26T14:32:58+00:00"}]
---

# Mautic: stored segment and custom field values enable PHP object injection

Mautic reads segment filter and custom field values from the database and unserializes them without restricting classes, so a crafted stored value can instantiate arbitrary PHP objects. With gadget chains from Mautic's dependencies, an attacker could potentially run code on the server and read, change or delete contact data.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- packagist:mautic/core affected >= 2.15.2, < 5.2.12; >= 6.0.0, < 6.0.10; >= 7.0.0, < 7.2.0 fixed 5.2.12, 6.0.10, 7.2.0

## How to check

Run 'composer show mautic/core' (or check the version in Mautic's admin footer/about) and compare: vulnerable if >=2.15.2 and <5.2.12, >=6.0.0 and <6.0.10, or >=7.0.0 and <7.2.0. Also review who holds segment/custom-field edit and API permissions, and audit recent changes to segment filters and custom fields.

## Fix

Upgrade to Mautic 5.2.12, 6.0.10 or 7.2.0 (per branch; Mautic 4 users: ELTS). No official workaround: restrict segment/custom-field management and API access to trusted users, and ensure no untrusted party can write to the Mautic database.

## Timeline

- 2026-10-26T14:30:36+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-115190
- 2026-10-26T14:32:58+00:00 analyst — Read Mautic GHSA-5r63-8h35-j3mw (primary): affected >=2.15.2,<5.2.12; >=6.0.0,<6.0.10; >=7.0.0,<7.2.0; fixed 5.2.12/6.0.10/7.2.0; no official workaround. No exploitation or PoC noted; social search skipped (no CVE-id conversation expected).

## Documents

- [advisory] Insecure Deserialization in Segment Filters and Custom Fields (GHSA-5r63-8h35-j3mw) https://github.com/mautic/mautic/security/advisories/GHSA-5r63-8h35-j3mw

## From the sources

An insecure deserialization (PHP object injection) vulnerability exists in Mautic's handling of segment filters and custom field properties. Several code paths that read these stored values from the database deserialize them without restricting which PHP classes may be instantiated, instead of using Mautic's safe deserialization helper. An attacker who is able to store a crafted serialized value in these segment filter or custom field properties can cause arbitrary PHP objects to be instantiated when Mautic later processes the data, for example during segment evaluation, contact export, or custom field API requests. Combined with gadget chains available in Mautic's dependencies, this could allow an attacker to execute arbitrary code on the server, read, modify, or delete data stored in the Mautic instance, including contact data, and affect its availability. Exploitation requires high privileges or an existing ability to write to the affected stored data.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_