CVE-2026-4776

Mautic has SQL Injection in API Contact Filtering

An authenticated user with API access can exploit this vulnerability to execute arbitrary SQL queries against the underlying database. This allows unauthorized retrieval of sensitive database contents, including user credentials, system configurations, and personal identifiable information (PII) of contacts, bypassing standard data access permissions.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-4776 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.2.11, 6.0.9, 7.1.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-4776? CVE-2026-4776 is a high-severity SQL injection vulnerability in mautic/core (composer), affecting versions >= 2.6.0, <= 4.4.13. It is fixed in 5.2.11, 6.0.9, 7.1.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-4776? CVE-2026-4776 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of mautic/core are affected by CVE-2026-4776? mautic/core (composer) versions >= 2.6.0, <= 4.4.13 is affected.
4. Is there a fix for CVE-2026-4776? Yes. CVE-2026-4776 is fixed in 5.2.11, 6.0.9, 7.1.2. Upgrade to this version or later.
5. Is CVE-2026-4776 exploitable, and should I be worried? Whether CVE-2026-4776 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-4776 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-4776?
   • Upgrade mautic/core to 5.2.11 or later
   • Upgrade mautic/core to 6.0.9 or later
   • Upgrade mautic/core to 7.1.2 or later

Other vulnerabilities in mautic/core