# CVE-2026-58002: WWBN AVideo Authorization Bypass via Users_affiliations add.json.php

> Authenticated attackers can forge affiliation records to bypass authorization checks and reassign video ownership to arbitrary users.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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:** 22 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-rg7g-cgjq-4wx8, GHSA-v8xr-qf65-qqxj

## What is CVE-2026-58002?

CVE-2026-58002 is a high-severity missing authorization vulnerability in WWBN AVideo, published on 22 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WWBN AVideo through commit 9c39d8c8b4c1f75540788d6b391740852ceb0732 contains an authorization bypass vulnerability in the Users_affiliations add.json.php endpoint that allows authenticated users to forge two-party consent records by supplying the counterparty's agreement timestamp. Attackers can create a forged affiliation with status='a' and then reassign video ownership to arbitrary users through the videoAddNew.json.php endpoint, which trusts the forged affiliation as an authorization term.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-58002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58002 is a high-severity missing authorization vulnerability in WWBN AVideo, published on 22 Aug 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-58002 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-58002/ (Markdown: https://insights.sbomify.com/CVE-2026-58002/index.md)
```

## Sources

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

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