Mautic has SQL Injection in API Contact Filtering

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

EPSS

• CVE-2026-4776: 0.22% estimated exploitation activity in the next 30 days; percentile 13.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

2 Jul 2026, 19:25 UTC

Last modified by the source

2 Jul 2026, 19:25 UTC

Source last checked

26 Oct 2026, 14:49 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fcmw-wx57-9p75

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-4776

Advisory: Mautic has SQL Injection in API Contact Filtering
IDs: CVE-2026-4776, GHSA-fcmw-wx57-9p75
Record: https://patchnext.com/advisories/cve-2026-4776 (revision 1, source checked 26 Oct 2026, 14:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: mautic/core 7.1.2, 6.0.9, 5.2.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist mautic/core: affected >= 2.6.0, <= 4.4.13; >= 5.0.0, < 5.2.11; >= 6.0.0, < 6.0.9; >= 7.0.0, < 7.1.2; fixed in 5.2.11, 7.1.2, 6.0.9

## Suggested inspection (read-only)
- Packagist mautic/core: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mautic/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fcmw-wx57-9p75 (GitHub-reviewed advisory GHSA-fcmw-wx57-9p75 lists affected ranges: Packagist mautic/core >=2.6.0 =5.0.0 =6.0.0 =7.0.0 <7.1.2)

Commands are suggestions: review each one before running it.