CVE-2026-4776 — core
HIGHCVE-2026-4776 is a high-severity (CVSS 7.1) SQL Injection vulnerability in mautic/core. A fix is available for mautic/core — see the affected versions and patch details below.
Mautic has SQL Injection in API Contact Filtering
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-4776.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-4776 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
mautic/core🐘mautic/core🐘mautic/core🐘mautic/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
An SQL injection vulnerability exists in Mautic's API contact filtering mechanism. Due to insufficient recursive sanitization of nested query parameters, an authenticated API user can bypass input filtering and inject arbitrary SQL commands.
Impact
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.
Patched Versions
This security issue has been fixed in the following releases:
- 7.1.2
- 6.0.9
- 5.2.11
- 4.4.20 ELTS
We strongly recommend upgrading to the latest version corresponding to your release branch.
Workarounds
There are no official workarounds. To mitigate this issue without upgrading, you may temporarily disable API access or restrict API permissions to highly trusted accounts.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | mautic/core | ≥ 2.6.0 | No fix |
| 🐘Packagist | mautic/core | ≥ 5.0.0&&< 5.2.11 | 5.2.11composer require mautic/core:^5.2.11 |
| 🐘Packagist | mautic/core | ≥ 6.0.0&&< 6.0.9 | 6.0.9composer require mautic/core:^6.0.9 |
| 🐘Packagist | mautic/core | ≥ 7.0.0&&< 7.1.2 | 7.1.2composer require mautic/core:^7.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mautic/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of mautic/core has shipped for CVE-2026-4776 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is CVE-2026-4776 in your dependencies?
Find it across Packagist, including transitive dependencies.