# CVE-2026-115195: A broken access control vulnerability exists in the Mautic Stats API (/api/stats/{table}).


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-7j28-9rg4-wg63

## What is CVE-2026-115195?

CVE-2026-115195 is a medium-severity vulnerability, published on 26 Oct 2026. 

### Official description

A broken access control vulnerability exists in the Mautic Stats API (/api/stats/{table}). The endpoint did not enforce permissions for several internal tables: an intended administrator-only restriction was never applied, and tables without an explicit permission mapping were readable by default. As a result, any authenticated API user, including one whose role grants no permissions, could read data from these tables, including the application audit log with actions performed by all users and change details that may contain contact personal data, stored visitor IP addresses and their geolocation details, and tracked redirect URLs and their channel mappings.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-115195 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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