Skip to main content

WWBN AVideo EUVDEUVD-2026-75415

| CVE-2026-88865 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-09-10 VulnCheck GHSA-f786-7wmv-h56x
8.6
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Authenticate with canStream-permission account
  2. Delivery
    Enumerate or enumerate restream object IDs via platform activity
  3. Exploit
    Send crafted request to getRestream.json.php with victim restream ID
  4. Install
    Receive token without ownership check
  5. C2
    Exchange token at getLiveKey.json.php
  6. Execute
    Extract victim's YouTube/Twitch stream key
  7. Impact
    Publish unauthorized content to victim's channel

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Attacker must hold a valid AVideo account with the canStream permission - a non-default, explicitly granted capability for streaming users. The target user must have configured at least one restream destination (YouTube, Twitch, or RTMP) with a stored stream key. No other special configuration is required beyond normal AVideo deployment with restreaming enabled. Exploitation is limited to authenticated canStream users; anonymous access or basic authenticated accounts without canStream cannot reach the vulnerable endpoints. The absence of ownership validation means no predictability of victim IDs is strictly necessary if the attacker can enumerate IDs through normal platform activity.

Impact

The CVSS 4.0 score of 8.6 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N) accurately reflects network-accessible, low-complexity exploitation requiring only a canStream-level account. The SC/SI metrics are scored N in the provided vector, but this may understate real-world impact: the exposed stream keys authenticate directly to YouTube/Twitch/RTMP endpoints - external systems - meaning subsequent-system confidentiality and integrity are also materially compromised. EPSS data is not provided; no KEV listing or confirmed active exploitation is noted. With no public POC and a relatively niche self-hosted platform, broad opportunistic exploitation is unlikely; however, within multi-tenant AVideo deployments (hosting companies, media organizations), a malicious canStream tenant could systematically harvest all other users' streaming credentials with minimal effort and no special tooling.

Exploit ScenarioDerived

An attacker with a low-privilege AVideo account that has canStream permission enumerates or guesses restream IDs belonging to other users, then sends crafted requests to getRestream.json.php specifying those IDs. The server returns valid tokens without checking ownership. The attacker exchanges each token against getLiveKey.json.php to extract stream keys, then uses those keys to go live on victims' YouTube or Twitch channels - potentially posting unauthorized content, disrupting legitimate broadcasts, or selling access to compromised streaming accounts.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 10, 2026

WWBN AVideo's restream subsystem allows any authenticated user holding canStream permission to mint authorization tokens for restream objects they do not own, by sending crafted requests to getRestream.json.php without ownership validation. Exchanging that token against getLiveKey.json.php exposes the victim's stored stream key for YouTube, Twitch, or arbitrary RTMP destinations - granting the attacker full publish access to another user's live streaming channel. No public exploit code has been identified at time of analysis, and the vulnerability is tracked by VulnCheck via GitHub security advisory GHSA-7jf4-mmqm-7p7x.

RemediationAI

Upgrade to a commit of WWBN AVideo that is more recent than c3edcc274c389816d434acadac07ee78eaf330c1, as this commit represents the last known-vulnerable state per EUVD-2026-75415. The GitHub security advisory at GHSA-7jf4-mmqm-7p7x is the authoritative source for the exact fixed revision; a specific tagged release version is not confirmed in the available data. As a compensating control until patching is possible, administrators of multi-tenant deployments should revoke canStream permissions from untrusted users and audit the getRestream.json.php and getLiveKey.json.php endpoints at the web-server layer (e.g., restrict them to whitelisted user sessions or block external access entirely if restream management is admin-only). Note that restricting these endpoints will disable restream functionality for legitimate users.

Affected VersionsENISA

AVideo 0 ≤c3edcc274c389816d434acadac07ee78eaf330c1

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

AVideo (CPE: cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*) is a self-hosted PHP video streaming platform that supports restreaming to external services via stored stream keys. The vulnerability is classified CWE-639 (Authorization Bypass Through User-Controlled Key), a classic IDOR pattern: the application issues a token keyed on a caller-supplied restream identifier without verifying that the authenticated user is the owner of that restream object. A two-step exploit chain leverages the token minting endpoint (getRestream.json.php) and the key retrieval endpoint (getLiveKey.json.php), both of which process the caller-supplied token without asserting ownership. The root cause is a missing server-side authorization check on a mutable, user-controlled identifier.

Know when Avideo gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.6 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 9.6 CRITICAL

PR:L for required canStream permission; S:C because the attacker's actions compromise other users' external streaming credentials and channels.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate restream ownership in getRestream.json.php, allowing authenticated users with canStream permission to mint tokens for arbitrary restreams. Attackers can exchange the token to retrieve other users' stream keys from getLiveKey.json.php and publish to their YouTube, Twitch, or RTMP destinations.

Technical POC Analysis

CWE-639 (Authorization Bypass Through User-Controlled Key), with CWE-862 (Missing Authorization) also assigned in the advisory.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

WWBN AVideo's restream subsystem allows authenticated users with streaming privileges to steal other broadcasters' stream keys (YouTube, Twitch, RTMP), enabling complete takeover of victims' live broadcast channels. Content creators face imminent risk of channel hijacking, audience impersonation, and lost revenue; organizations running AVideo as broadcast infrastructure should treat this as a critical access control failure until patched.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict canStream permission to administrators only, enforcing least-privilege access for broadcasters, (2) implement API audit logging and alerting on restream endpoints to flag unauthorized token requests, (3) establish mandatory monthly stream key rotation across all YouTube, Twitch, and RTMP accounts, (4) apply network segmentation and IP whitelisting to AVideo APIs if available, (5) monitor for anomalous patterns (multiple token requests per user, requests from unusual locations/times) via SIEM.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Low
niche self-hosted video streaming platform, limited enterprise footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

More in Avideo

View all
CVE-2023-48728 CRITICAL POC
9.6 Jan 10

A cross-site scripting (xss) vulnerability exists in the functiongetOpenGraph videoName functionality of WWBN AVideo 11.

CVE-2024-31819 CRITICAL POC
9.8 Apr 10

An issue in WWBN AVideo v.12.4 through v.14.2 allows a remote attacker to execute arbitrary code via the systemRootPath

CVE-2022-30547 CRITICAL POC
9.9 Aug 22

A directory traversal vulnerability exists in the unzipDirectory functionality of WWBN AVideo 11.6 and dev master commit

CVE-2023-49599 CRITICAL POC
9.8 Jan 10

An insufficient entropy vulnerability exists in the salt generation functionality of WWBN AVideo dev master commit 15fed

CVE-2026-28501 CRITICAL POC
9.8 Mar 06

Unauthenticated SQL injection in AVideo before 24.0.

CVE-2023-25313 CRITICAL POC
9.8 Apr 25

OS injection vulnerability in World Wide Broadcast Network AVideo version before 12.4, allows attackers to execute arbit

CVE-2022-26842 CRITICAL POC
9.6 Aug 22

A reflected cross-site scripting (xss) vulnerability exists in the charts tab selection functionality of WWBN AVideo 11.

CVE-2023-47861 CRITICAL POC
9.0 Jan 10

A cross-site scripting (xss) vulnerability exists in the channelBody.php user name functionality of WWBN AVideo 11.6 and

CVE-2022-28712 CRITICAL POC
9.0 Aug 22

A cross-site scripting (xss) vulnerability exists in the videoAddNew functionality of WWBN AVideo 11.6 and dev master co

CVE-2023-49589 HIGH POC
8.8 Jan 10

An insufficient entropy vulnerability exists in the userRecoverPass.php recoverPass generation functionality of WWBN AVi

CVE-2023-32073 HIGH POC
8.8 May 12

WWBN AVideo is an open source video platform. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable

CVE-2023-30854 HIGH POC
8.8 Apr 28

AVideo is an open source video platform. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy