# CVE-2026-115192: An SQL Injection vulnerability exists in the dashboard widget data API endpoint (/api/data/{type}).


- **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-qpmx-7pq3-5q2v

## What is CVE-2026-115192?

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

### Official description

An SQL Injection vulnerability exists in the dashboard widget data API endpoint (/api/data/{type}). Chart filter parameters supplied by the client are not properly validated before they are used in the database queries that build dashboard chart data. An authenticated user with API access can exploit this to inject SQL into these reporting queries. Using blind SQL injection techniques, the attacker can read arbitrary data from the Mautic database, including contact and other marketing data and user account data with password hashes. The injected SQL can also be used to slow down database queries, which can have a limited impact on availability. Data modification is not possible through this vulnerability. Exploitation requires the Mautic API to be enabled.

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

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


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

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

## Is CVE-2026-115192 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115192 is a high-severity vulnerability, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115192 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-115192/ (Markdown: https://insights.sbomify.com/CVE-2026-115192/index.md)
```

## Sources

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

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