# CVE-2026-86810: Open-Web-Analytics Controller Controller.php checkCapabilityAndAuthenticateUser improper authentication


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-vq6x-7g8m-7qhj

## What is CVE-2026-86810?

CVE-2026-86810 is a medium-severity vulnerability in Open-Web-Analytics, published on 8 Sep 2026. 

### Official description

A vulnerability was detected in Open-Web-Analytics up to 1.9.1. The impacted element is the function checkCapabilityAndAuthenticateUser of the file Core/Controller.php of the component Controller. Performing a manipulation results in improper authentication. The attack may be initiated remotely. Upgrading to version 1.10.0 is sufficient to resolve this issue. The patch is named 6fc91c49eebdb8bfdfeed71cb50a5d97eac70f24. It is advisable to upgrade the affected component.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-86810 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86810 is a medium-severity vulnerability in Open-Web-Analytics, published on 8 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-86810 in the wild and no public exploit code.

Affected product: Open-Web-Analytics. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-86810/ (Markdown: https://insights.sbomify.com/CVE-2026-86810/index.md)
```

## Sources

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

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