CVE-2026-4776
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMautic contains an SQL injection vulnerability in its API contact filtering mechanism. The issue stems from insufficient recursive sanitization of nested query parameters, allowing authenticated API users to bypass input filtering and inject arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Mautic installationIdentify if Mautic is running in your environment by checking for Mautic-specific files (e.g., app/app.php, vendor/autoload.php) or the Mautic web application response headers.Affected if Mautic is not present in the environment.
-
Check installed Mautic versionLocate the version file (typically app/version.txt or through the Mautic admin dashboard under System Info) and compare the version number against the affected range published in the CVE advisory.Affected if The installed version falls within the affected version range and has not been patched.
-
Verify API functionality is enabledCheck the Mautic configuration file (app/config/local.php or through the UI at Settings > API Settings) for API enablement settings, or attempt a simple API request to confirm API access is active.Affected if The API is disabled, the vulnerability cannot be exploited through the API interface.
-
Confirm API authentication is accessibleTest API access using a valid API key or OAuth credentials against the contacts endpoint (e.g., GET /api/contacts) to verify authenticated API users can interact with contact filtering.Affected if API authentication is not configured or all API users are restricted from accessing contact endpoints.
-
Inspect logs for nested filter parameter patternsReview Mautic access logs and application logs (var/logs/) for requests containing nested filter parameters in the API contact endpoint, such as filter[0][field][nested][field] structures that may indicate exploitation attempts.Affected if Suspicious nested filter parameter patterns are found in logs without corresponding legitimate API usage.
The environment is affected if Mautic is running a version within the CVE-affected range, the API is enabled and accessible to authenticated users, and the contact filtering API endpoint can accept nested filter parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper recursive input sanitization for all nested query parameters in the API filtering logic, or use parameterized queries/prepared statements to eliminate SQL injection vectors.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4776 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4776 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data