Skip to main content

Mautic EUVDEUVD-2026-109793

| CVE-2026-115190 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-10-26 Mautic
8.0
CVSS 3.1 · Vendor: Mautic
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as high-privileged Mautic user
  2. Delivery
    Store crafted serialized payload in segment filter or custom field
  3. Exploit
    Trigger processing via segment evaluation, export, or API
  4. Execution
    Instantiate gadget-chain PHP objects
  5. Impact
    Execute arbitrary code on server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must be able to store a crafted serialized value in Mautic's segment filter or custom field properties, which per the advisory requires high privileges (PR:H) - administrative permissions to manage segments and custom fields, API write access to those objects, or direct write access to the Mautic database. The injected payload only fires when Mautic subsequently processes the stored data: during segment evaluation, contact export, or custom field API requests. Full remote code execution additionally depends on a usable gadget chain being present in Mautic's dependencies; without a suitable chain the impact may be limited to object instantiation side effects. The primary limiting factors are the high-privilege/write prerequisite and the gadget-chain dependency; no end-user interaction is required (UI:N).

Impact

Severity is High (CVSS 8.0, CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H), but the real-world priority is tempered by the access gate. The vector is network-reachable (AV:N) and scope-changing (S:C, consistent with code execution escaping the application to the host OS), yet exploitation requires high privileges (PR:H) - an account able to write to segment-filter or custom-field properties, or direct database write access - and the advisory itself notes full code execution is 'combined with gadget chains available in Mautic's dependencies', which aligns with the AC:H rating. There is no CISA KEV entry, so this is 'no public exploit identified at time of analysis'; no EPSS score was supplied, so widespread-exploitation probability cannot be quantified from the input. The only reference is the vendor GHSA advisory, not a working exploit. The vuln.today decision label is 'this_week', indicating prompt patching rather than an emergency. Net: a genuine high-impact RCE/data-compromise issue, but one gated behind privileged access and a usable gadget chain, so it is best treated as a this-week remediation priority rather than an internet-facing drive-by, and most dangerous as a privilege-escalation / insider or post-compromise vector.

Exploit ScenarioDerived

A high-privileged Mautic user, a compromised admin/API account with rights to manage segments or custom fields, or any party with write access to the Mautic database stores a crafted serialized value in a segment filter or custom field property. When Mautic later processes that data (segment evaluation, contact export, or a custom field API request), the unrestricted deserialization instantiates arbitrary PHP objects whose magic methods run automatically, and combined with a dependency gadget chain this can execute arbitrary code on the server. No public exploit was identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 26, 2026

PHP object injection in Mautic's segment filters and custom field properties can escalate to server-side code execution because stored serialized values are deserialized without class restrictions and Mautic's dependencies may supply usable gadget chains. The flaw affects Mautic core versions before 5.2.12, 6.0.10 and 7.2.0; exploitation requires high privileges or an existing ability to write the affected stored data, and the payload fires when Mautic later evaluates segments, exports contacts or serves custom field API requests. No public exploit was identified at the time of analysis, and the vendor advisory lists fixed releases for each maintained branch.

RemediationAI

Upgrade Mautic to the fixed release for the deployed branch: 7.2.0 for the 7.x line, 6.0.10 for the 6.x line, or 5.2.12 for the 5.x line, as listed in vendor advisory GHSA-5r63-8h35-j3mw. The advisory states there are no official workarounds; to reduce risk without upgrading, restrict administrative access, including permissions to manage segments and custom fields and API access, to trusted users, and ensure no untrusted party has write access to the Mautic database. Mautic 4 users should refer to the vendor's ELTS program because the advisory's fixed versions do not cover that legacy branch.

Affected ProductsAI

Mautic core is affected across the advisory's listed Composer package ranges: versions from 2.15.2 up to but not including 5.2.12, versions from 6.0.0 up to but not including 6.0.10, and versions from 7.0.0 up to but not including 7.2.0. The vendor advisory is GHSA-5r63-8h35-j3mw at https://github.com/mautic/mautic/security/advisories/GHSA-5r63-8h35-j3mw. Mautic 4 is outside the listed fixed branches and the advisory points legacy Mautic 4 users to the vendor's Extended Long Term Support (ELTS) program.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This is a CWE-502 insecure deserialization issue in Mautic, a PHP-based marketing automation platform. Several code paths read segment filter and custom field property values from the database and pass them to PHP deserialization without restricting which classes may be instantiated, rather than using Mautic's safe deserialization helper. When arbitrary objects are instantiated, PHP magic methods such as wakeup or destructor methods can run automatically; if a suitable gadget chain exists in Mautic's Composer dependencies, this can lead to arbitrary code execution, data access or availability impact. The assessed vector is CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H: network reachable, high attack complexity, high privileges required, no user interaction, scope changed, and high confidentiality, integrity and availability impact. The high privilege requirement reflects the need to store a crafted serialized value through administrative segment or custom field permissions, API write access to those objects, or direct database write access. The advisory's package data identifies composer/mautic/core as vulnerable in >= 2.15.2, < 5.2.12; >= 6.0.0, < 6.0.10; and >= 7.0.0, < 7.2.0.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Mautic) PRIMARY 8.0 HIGH
AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 8.0 HIGH

AV:N via API/web processing, PR:H because writing the serialized value needs high privileges, AC:H as full RCE depends on a suitable dependency gadget chain, S:C since code execution escapes to the host.

3.1 AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Mautic).

CVSS VectorVendor: Mautic

Attack Vector
Network
Attack Complexity
High
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Technical POC Analysis

CWE-502, Deserialization of Untrusted Data in Mautic application code (mautic/core, Composer package), not in a third-party library.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

A high-severity vulnerability in Mautic's segment filters and custom fields could allow attackers with high privileges to execute arbitrary code on the server, potentially leading to full system compromise. Leadership should prioritize patching because this affects marketing operations and customer data integrity.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.5%
Top 58% exploitable
Prevalence
Medium
popular open-source self-hosted marketing automation, moderate real-world footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy