# CVE-2026-81733: WWBN AVideo through 30.0 CSRF via myLiveControls.save.json.php

> An attacker can trick a logged-in streamer into changing live-channel redirect settings, potentially redirecting viewers to phishing sites.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** GHSA-mqr3-w6qc-2c4f, GHSA-wpr3-456q-6vgc

## What is CVE-2026-81733?

CVE-2026-81733 is a medium-severity vulnerability in WWBN AVideo, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

WWBN AVideo through 30.0 (and master up to commit 4cb576e) contains a cross-site request forgery vulnerability in plugin/Live/myLiveControls.save.json.php. The endpoint only checks that a user is logged in and processes customUrl, customMessage, and autoRedirect parameters from $_REQUEST via a GET request without enforcing a CSRF token or origin check. An attacker who lures a logged-in streamer to a malicious page can silently change the live-channel viewer-redirect settings (persisted in users.externalOptions), causing viewers to be redirected to a phishing site or shown a spoofed message.

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

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


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

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

## Is CVE-2026-81733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81733 is a medium-severity vulnerability in WWBN AVideo, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81733 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-81733/ (Markdown: https://insights.sbomify.com/CVE-2026-81733/index.md)
```

## Sources

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

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