CVE-2026-115190

Insecure Deserialization in Mautic Segment Filters Allow Arbitrary PHP Object Injection

Published Oct 26, 2026 CVSS 3.1 · 8 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

An insecure deserialization flaw in Mautic allows an attacker who can store a crafted serialized value in segment filters or custom field properties to trigger the instantiation of arbitrary PHP objects. Because the deserialization does not restrict allowed classes, an attacker can chain gadget objects present in Mautic dependencies to execute arbitrary code on the server, potentially reading, modifying, or deleting data such as contact information and disrupting service availability. This flaw exposes the full range of confidentiality, integrity and availability risks inherent to code execution on the web application.

Affected Systems

Mautic is affected; all installations that use the segment filter or custom field mechanisms are vulnerable. The specific version range is not documented in the advisory, so all currently installed Mautic instances should be considered at risk.

Risk and Exploitability

The CVSS score of 8 indicates a high severity. EPSS data is unavailable, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires an attacker to have high‑privilege or write access to the affected database fields, so the attack vector is likely internal or through an authenticated compromised account. If these conditions are met, the attacker can achieve remote code execution and full data compromise.

Remediation

Vendor Workaround

There are no official workarounds. To reduce the risk without upgrading, restrict administrative access (including permissions to manage segments and custom fields, and API access) to trusted users, and make sure no untrusted party has write access to the Mautic database.


OpenCVE Recommended Actions

  • Apply the latest Mautic patch or upgrade to a version that fixes the deserialization vulnerability.
  • Restrict administrative privileges so that only trusted users can manage segments, custom fields, and API access.
  • Ensure that no untrusted party has write permissions to the Mautic database or the application’s data tables.
  • Monitor application logs for suspicious deserialization attempts or unexpected object instantiation.

Generated by OpenCVE AI on October 26, 2026 at 15:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Mautic
Mautic mautic
Vendors & Products Mautic
Mautic mautic
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Insecure Deserialization in Mautic Segment Filters Allow Arbitrary PHP Object Injection
Type Values Removed Values Added
Description 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.
Weaknesses CWE-502
References
Metrics cvssV3_1

{'score': 8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
Mautic
Published
Updated
Oct 26, 2026, 3:35 PM
Reserved
Oct 22, 2026, 6:39 AM
Status
Deferred
Published
Oct 26, 2026, 2:16 PM
Modified
Oct 26, 2026, 4:17 PM