# CVE-2026-59256: WWBN AVideo Unbound Token Authorization Bypass via Gallery

> Attackers can bypass authorization checks by obtaining unbound tokens from the Gallery endpoint to access restricted video content.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-v366-95x7-75w9, GHSA-wq57-wxcr-rx6v

## What is CVE-2026-59256?

CVE-2026-59256 is a high-severity authentication bypass vulnerability in WWBN AVideo, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WWBN AVideo through commit 9c39d8c8 contains an authorization bypass vulnerability where getToken() creates tokens without binding to user identity or purpose, and plugin/Gallery/view/sections.php issues valid tokens to unauthenticated visitors. Attackers can retrieve a token from the Gallery endpoint and use it to bypass authorization checks in other subsystems like view/hls.php to access restricted video content.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-59256 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59256 is a high-severity authentication bypass vulnerability in WWBN AVideo, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59256 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-59256/ (Markdown: https://insights.sbomify.com/CVE-2026-59256/index.md)
```

## Sources

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

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