GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
Check your stack
GHSA-fcmw-wx57-9p75high7.1

Mautic has SQL Injection in API Contact Filtering

Impact

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.

Source excerpt · OSV

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

mautic/core Packagist
Affected rangeRecorded fix
From 2.6.0 through 4.4.13 (inclusive)Ecosystem versionsNot recorded
From 5.0.0 before 5.2.11Ecosystem versions5.2.11
From 6.0.0 before 6.0.9Ecosystem versions6.0.9
From 7.0.0 before 7.1.2Ecosystem versions7.1.2

Version evidence: OSV · GHSA-fcmw-wx57-9p75

View original version evidence (146 explicit versions)

Original source 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.

References