# CVE-2026-58001: WWBN AVideo Cross-Site Request Forgery via videoEditLight.php

> Attackers can hijack video ownership via CSRF when administrators view malicious video descriptions in AVideo.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-6g67-433v-cf8h, GHSA-7mqw-mqc3-ffjw

## What is CVE-2026-58001?

CVE-2026-58001 is a medium-severity vulnerability in WWBN AVideo, published on 22 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

WWBN AVideo through commit 9c39d8c8 contains a cross-site request forgery vulnerability in objects/videoEditLight.php that lacks request authenticity checks and accepts GET requests. Attackers can store an img tag in a video description that transfers video ownership to an attacker-controlled account when an administrator views the video page.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-58001 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58001 is a medium-severity vulnerability in WWBN AVideo, published on 22 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-58001 in the wild and no public exploit code.

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

## Sources

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

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