# CVE-2026-92585: AVideo through 29.0 Missing Authorization Check via API Like Endpoint

> Logged-in users can vote on restricted videos via the API, bypassing access controls and modifying vote counters.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-hgf3-hf6h-jm9r, GHSA-rrcx-6vw7-xwj8

## What is CVE-2026-92585?

CVE-2026-92585 is a medium-severity missing authorization vulnerability in WWBN AVideo, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AVideo through 29.0 (commit c3edcc274c389816d434acadac07ee78eaf330c1) fails to validate video access permissions in the API like endpoint, allowing logged-in users to vote on password-protected and group-restricted videos. Attackers can submit like and dislike requests to increment vote counters on videos they cannot watch by calling the set.json.php endpoint with APIName parameters.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92585 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92585 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92585 is a medium-severity missing authorization vulnerability in WWBN AVideo, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92585 exists.

Affected product: WWBN AVideo. 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-92585/ (Markdown: https://insights.sbomify.com/CVE-2026-92585/index.md)
```

## Sources

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

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