Skip to main content
← Vulnerabilities

WWBN AVideo through 29.7.1 Missing Authorization via Live Restream Endpoints

Affects WWBN AVideo 12.4 through 29.7.1 and current master with default Live plugin settings, where a user with canStream can obtain other users' stream keys. No fixed version is listed in the facts.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

8.6HighCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Default Live plugin settings Attacker is a user with canStream who owns one restream destination Affected range 12.4 through 29.7.1 and current master

Published
Last modified
Reference
Last checked
17/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

WWBN AVideo, a video platform, has a missing authorization flaw in the Live plugin's restream endpoints. An attacker who can log in as a streamer can reach it remotely, and can use it to obtain other users' stream keys and HLS URLs, then publish as the victim or restream private or pay-per-view lives.

Read the original description

WWBN AVideo through 29.7.1 contains a missing authorization vulnerability in Live plugin restream endpoints that allows authenticated streamers to obtain other users' stream keys by supplying arbitrary live_transmitions_history_id values. Attackers can redeem the issued action tokens at verifyTokenForAction.json.php to retrieve victims' HLS URLs and stream keys, then publish as the victim or restream private or pay-per-view lives.

Who should check

Teams running WWBN AVideo through 29.7.1 with the Live plugin, including streamers and admins who host private or pay-per-view lives

Read the source excerpt

“Affecting AVideo <= 29.7.1”

vulncheck.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.6/10CVSS 8.6
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Default Live plugin settings Attacker is a user with canStream who owns one restream destination Affected range 12.4 through 29.7.1 and current master
  • Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126541 (WWBN AVideo through 29.7.1 Missing Authorization via Live Restream Endpoints), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126541 (entry last updated 2026-11-11):
Affected:
- WWBN AVideo: through 29.7.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Default Live plugin settings (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-233c-vfmw-6rw9)
- Attacker is a user with canStream who owns one restream destination (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-233c-vfmw-6rw9)
- Affected range 12.4 through 29.7.1 and current master (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-233c-vfmw-6rw9)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126541 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126541 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/WWBN/AVideo/security/advisories/GHSA-233c-vfmw-6rw9
- https://github.com/WWBN/AVideo/commit/be9d70199279aafe5062744d319fd4df4e5f7a48
- https://github.com/WWBN/AVideo/blob/v29.7.1/plugin/Live/view/getRestream.json.php#L27-L48
- https://github.com/WWBN/AVideo/blob/v29.7.1/plugin/Live/view/Live_restreams/verifyTokenForAction.json.php#L30-L56
- https://www.vulncheck.com/advisories/wwbn-avideo-through-29.7.1-missing-authorization-via-live-restream-endpoints
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126541
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-126541.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • WWBN AVideo

    through 29.7.1

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Patch
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126541

Is CVE-2026-126541 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A user with canStream who owns one restream destination can obtain other users' stream keys and HLS URLs. This includes private, unlisted, group-restricted and pay-per-view lives, which could then be republished or restreamed.Source: github.com

Which versions are affected by CVE-2026-126541?

AVideo: through 29.7.1.Source: cve.now feed data

Am I affected, and how do I check?

The stated affected range is AVideo 12.4 through 29.7.1 and current master, under default Live plugin settings. Check the installed AVideo version and whether the Live plugin uses default settings to compare against this range.Source: github.com

How do I fix CVE-2026-126541?

The facts do not name a fixed version or an upgrade target, so no specific upgrade is given. Check the vendor's advisory for a patched release.Source: github.com