CVE-2026-4776
SQL Injection in Mautic API via Unsanitized Contact Filtering
Publication date: 2026-05-29
Last updated on: 2026-05-29
Assigner: Mautic
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mautic | mautic | From 2.6.0 (inc) |
| mautic | mautic | 4.4.20 |
| mautic | mautic | 5.2.11 |
| mautic | mautic | 6.0.9 |
| mautic | mautic | 7.1.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-4776 is a high-severity SQL injection vulnerability found in Mautic's API contact filtering mechanism.
The vulnerability occurs because nested query parameters are not sufficiently sanitized, allowing an authenticated API user to bypass input filtering.
This bypass enables the injection of arbitrary SQL commands into the database queries.
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized execution of SQL queries against the database.
This may result in exposure of sensitive data such as user credentials, system configurations, and personally identifiable information (PII) of contacts.
The vulnerability has a CVSS score of 7.1, indicating a high severity impact primarily on confidentiality.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2026-4776 vulnerability, you should upgrade Mautic to one of the patched versions: 7.1.2, 6.0.9, 5.2.11, or 4.4.20.
If upgrading immediately is not possible, temporary mitigations include disabling API access or restricting API permissions to trusted accounts only.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in Mautic's API contact filtering mechanism can lead to unauthorized execution of SQL queries, potentially exposing sensitive data such as personally identifiable information (PII) of contacts. Exposure of PII can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding sensitive personal data against unauthorized access.
Therefore, if exploited, this vulnerability could compromise confidentiality and lead to violations of common standards and regulations that mandate protection of sensitive information.