llamaCVEVulnerability Intelligence
/
mautic/core

CVE-2026-115190

An insecure deserialization (PHP object injection) vulnerability exists in Mautic's handling of segment filters and custom field properties

Specific setups onlyParche disponibleunsafe deserialization
Descargar PNG JSON
CVSS 3.1
8.0
Alta
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versiones5.2.12 · 6.0.10 · 7.2.0
Exposición24 dDesde la divulgación, 26 oct 2026, 7:41 a. m.
Detección1 hDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +2
Explotación
Remediación
Monitoreo
Detectada +2
Fuente: OSV +1
26 oct 26
19 nov 26
26 oct 26
1 nov 26
7 nov 26
13 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-115190 divulgada · CVSS 8 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Fuente: ENISA EUVD Registro visto por primera vez en ENISA EUVD
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen

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.

Affects Mautic core 2.15.2 up to 5.2.12, 6.0.0 up to 6.0.10, and 7.0.0 up to 7.2.0. Fixed in 5.2.12, 6.0.10, and 7.2.0.

¿Qué significa?Mautic does not safely handle serialized data in segment filter or custom field properties. A party who can store a crafted serialized value there can cause arbitrary PHP objects to be created, which can lead to code execution on the server, reading, modifying or deleting instance data including contact data, and disruption of availability through gadget chains in dependencies.
¿Quién está afectado?Mautic core versions 2.15.2 up to 5.2.12, 6.0.0 up to 6.0.10, and 7.0.0 up to 7.2.0 are in the affected range. The relevant setup is one where the ability to store values in segment filters or custom field properties is open to untrusted parties, which is controlled by administrative and API permissions. The installed mautic/core version can be checked in the composer.lock file or the Mautic version shown in the admin area.
¿Qué hacer?Upgrade to 5.2.12, 6.0.10, or 7.2.0, whichever matches the release line in use. The vendor states there are no official workarounds, but until the upgrade is applied, restricting administrative and API access, including permissions to manage segments and custom fields, to trusted users reduces the risk.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Affected Mautic core versions: 2.15.2 up to 5.2.12, 6.0.0 up to 6.0.10, and 7.0.0 up to 7.2.0.“>= 2.15.2, < 5.2.12”
02
An attacker must be able to store a crafted serialized value in segment filter or custom field properties.“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”
¿Quién debe revisar?Teams running mautic/core (Composer) versions 2.15.2 through 5.2.12, 6.0.0 through 6.0.10, or 7.0.0 through 7.2.0 and users with high privileges to manage segments or custom fields.
MitigaciónRestrict 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.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:H
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
mautic/core≥ 2.15.2 < 5.2.12
mautic/core≥ 6.0.0 < 6.0.10
mautic/core≥ 7.0.0 < 7.2.0
2.15.2
5.2.12
6.0.0
6.0.10
7.0.0
7.2.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
mautic/core
Corregida 5.2.12, 6.0.10, 7.2.0 — —
Versiones corregidas5.2.126.0.107.2.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Registro
EscenarioGENERALMautic
MitigaciónThere 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.Mautic
Referencias
Fabricantehttps://github.com/mautic/mautic/security/advisories/GHSA-5r63-8h35-j3mw

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.