Description
A SQL injection vulnerability exists in a contact lookup AJAX endpoint of the Mautic administration interface (/s/ajax). A request parameter that selects the contact field to search by is not properly validated before it is used in a database query. Any authenticated Mautic user can exploit this, regardless of the role or permissions assigned to the account. Using blind (boolean-based or time-based) techniques, the attacker can run arbitrary SQL queries against the Mautic database and read any data the Mautic database user can access, including Mautic user accounts with email addresses and password hashes, contact data, and campaign and email content.
Published: 2026-10-26
Score: 7.1 High
EPSS: n/a
KEV: No
Impact: Data confidentiality compromise through SQL injection that any authenticated user can exploit.
Action: Patch
AI Analysis

Impact

Mautic exposes a contact lookup AJAX endpoint (/s/ajax) that accepts a request parameter specifying the field to search by. The parameter is not validated before it is concatenated into an SQL query, allowing blind SQL injection. An attacker who is able to authenticate to Mautic, regardless of role, can run arbitrary boolean‑based or time‑based queries to read data that the Mautic database user can access, such as user accounts, email addresses, hashes, contact details, and campaign or email content. This leads to a full disclosure of sensitive data stored in the Mautic database.

Affected Systems

The vulnerability affects the Mautic web application, specifically its administration interface. No specific version range is listed in the data; any installation using the unpatched /s/ajax endpoint is potentially affected.

Risk and Exploitability

The CVSS v3.1 score of 7.1 indicates a high risk of exploitation, and the EPSS score is not available, so the likelihood cannot be quantified. The flaw is listed as not being in CISA KEV, meaning there is no documented widespread exploitation. The only prerequisite for exploitation is authentication, and there are no role or permission restrictions, making it accessible to any Mautic user. Attackers would need to use blind SQL techniques, but the database response time can be used to infer information.

Generated by OpenCVE AI on October 26, 2026 at 15:54 UTC.

Remediation

Vendor Workaround

There are no official workarounds. To reduce the risk without upgrading, limit Mautic user accounts to trusted users, deactivate unused accounts, and enforce strong passwords. Where possible, block requests to /s/ajax with the action lead:getLeadIdsByFieldValue at the web server or web application firewall level. This only disables the duplicate contact warning shown when editing unique identifier fields in the contact form.


OpenCVE Recommended Actions

  • Install the newest Mautic release that fixes the SQL injection flaw.
  • If an upgrade is not yet possible, restrict Mautic user accounts to trusted users, deactivate unused accounts, and enforce strong passwords to limit the attack surface.
  • Block requests to /s/ajax with the action lead:getLeadIdsByFieldValue at the web server or web application firewall level, preventing the duplicate contact warning endpoint from being reachable.

Generated by OpenCVE AI on October 26, 2026 at 15:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 26 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Mautic
Mautic mautic
Vendors & Products Mautic
Mautic mautic

Mon, 26 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 26 Oct 2026 16:15:00 +0000

Type Values Removed Values Added
Title SQL Injection in Mautic Contact Lookup Endpoint

Mon, 26 Oct 2026 14:00:00 +0000

Type Values Removed Values Added
Description A SQL injection vulnerability exists in a contact lookup AJAX endpoint of the Mautic administration interface (/s/ajax). A request parameter that selects the contact field to search by is not properly validated before it is used in a database query. Any authenticated Mautic user can exploit this, regardless of the role or permissions assigned to the account. Using blind (boolean-based or time-based) techniques, the attacker can run arbitrary SQL queries against the Mautic database and read any data the Mautic database user can access, including Mautic user accounts with email addresses and password hashes, contact data, and campaign and email content.
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Mautic

Published:

Updated: 2026-10-26T15:35:53.390Z

Reserved: 2026-10-22T06:39:18.823Z

Link: CVE-2026-115191

cve-icon Vulnrichment

Updated: 2026-10-26T15:33:55.054Z

cve-icon NVD

Status : Deferred

Published: 2026-10-26T14:16:30.490

Modified: 2026-10-26T16:17:16.447

Link: CVE-2026-115191

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-26T16:30:10Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')