Skip to main content
VulnerabilityPublished

CVE-2026-115195: mautic/core · Missing Authorization

Affects mautic/coreSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium · fixed in 7.2.2 : update mautic/core when convenient.

Data as of 26 Oct 2026, 15:55 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 7.2.2, 6.0.10, 5.2.12
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade mautic/core to 7.2.2, 6.0.10 or 5.2.12.

Affected software

ProductAffectedFixed in
mautic/coreAffected
  • >=7.0.0 <7.2.2
Fixed in
  • 7.2.2
mautic/coreAffected
  • >=6.0.0 <6.0.10
Fixed in
  • 6.0.10
mautic/coreAffected
  • >=2.3.0 <5.2.12
Fixed in
  • 5.2.12
Packagistmautic/corepkg:composer/mautic/coreOther threatsAffected
  • >=2.3.0 <5.2.12
  • >=6.0.0 <6.0.10
  • >=7.0.0 <7.2.2
Fixed in
  • 5.2.12
  • 6.0.10
  • 7.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix for this vulnerability is available in Mautic core versions 5.2.12, 6.0.10, and 7.2.2. Users should upgrade to one of these versions or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Description

A broken access control vulnerability exists in the Mautic Stats API (/api/stats/{table}). The endpoint did not enforce permissions for several internal tables: an intended administrator-only restriction was never applied, and tables without an explicit permission mapping were readable by default. As a result, any authenticated API user, including one whose role grants no permissions, could read data from these tables, including the application audit log with actions performed by all users and change details that may contain contact personal data, stored visitor IP addresses and their geolocation details, and tracked redirect URLs and their channel mappings.

References

Community reviews

Loading reviews…