# CVE-2026-115191: A SQL injection vulnerability exists in a contact lookup AJAX endpoint of the Mautic administration interface (/s/ajax).


- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-fj8v-c9c3-7q26

## What is CVE-2026-115191?

CVE-2026-115191 is a high-severity vulnerability, published on 26 Oct 2026. 

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-115191?


## How do I fix CVE-2026-115191?

No fix has been published for CVE-2026-115191 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115191 being exploited?

There is no known exploitation of CVE-2026-115191 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115191 and fix it if it is affected.

What it is: CVE-2026-115191 is a high-severity vulnerability, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115191 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115191/ (Markdown: https://insights.sbomify.com/CVE-2026-115191/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115191
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115191
- OSV: https://osv.dev/vulnerability/CVE-2026-115191

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115191/
Summaries are generated and may contain mistakes; the official description above is the record.