Read the docs
TI-2026-80375 Aliases CVE-2026-115190

PHP object injection in Mautic segment filters and custom fields

Priority LOW 37CWE-502Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
High
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-502.

Summary

Mautic core versions from 2.15.2 before 5.2.12, from 6.0.0 before 6.0.10, and from 7.0.0 before 7.2.0 are affected by insecure PHP object deserialization (CWE-502). Several code paths read segment filter and custom field properties from the database and deserialize them without restricting which classes may be instantiated. An attacker who can store a crafted serialized value in these properties can cause arbitrary PHP objects to be created when Mautic processes the data, which may allow code execution on the server. Exploitation requires high privileges or an existing ability to write to the affected stored data.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00489 42nd percentileScored 2026-11-07
Fix Fixed mautic/core: 5.2.12, 6.0.10, 7.2.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
—mautic/core2.15.2 to before 5.2.12; 6.0.0 to before 6.0.10; 7.0.0 to before 7.2.05.2.12, 6.0.10, 7.2.0Patch availableCNA
  • mautic/core Vendor— Affected 2.15.2 to before 5.2.12; 6.0.0 to before 6.0.10; 7.0.0 to before 7.2.0 Fixed in 5.2.12, 6.0.10, 7.2.0 Patch available CNA

Remediation

Upgrade mautic/core to 5.2.12, 6.0.10, or 7.2.0, depending on the installed release branch.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

  • Fix · CNA mautic/core Fixed in 5.2.12, 6.0.10, 7.2.0

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-26 Threatist record created from CVE-2026-115190
  2. 2026-10-26 CISA SSVC decision points changed
  3. 2026-10-26 Priority changed: MEDIUM → LOW
  4. 2026-11-06 Affected versions changed · Red Hat
  5. 2026-11-06 CVSS score added · Red Hat

References

Sources