Skip to main content

WWBN AVideo EUVDEUVD-2026-75425

| CVE-2026-88875 MEDIUM
Exposure of Private Personal Information to an Unauthorized Actor (CWE-359)
2026-09-10 VulnCheck GHSA-v87w-4w8w-g5fx
5.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

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

  1. Access
    Register low-privilege AVideo account
  2. Delivery
    Authenticate and obtain session
  3. Exploit
    Send APIName=video request for target user's video
  4. Execution
    Receive JSON response with owner email, username, privilege flags
  5. Impact
    Map admin accounts for follow-on targeting

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection PII protection
Exploitation Conditions

Exploitation requires a valid low-privilege authenticated session on the target AVideo instance - the attacker must hold any registered account. The target video must be accessible to the API (i.e., a video owned by another user that the caller can reference by ID). No special server configuration, non-default settings, or elevated privileges are required beyond basic account registration. Exploitation is limited to instances that permit user account creation by untrusted parties; instances with closed registration or restricted to a trusted internal user base are meaningfully less exposed. The disclosed data is read-only (C:L, I:N, A:N) - this vulnerability does not enable write access, authentication bypass, or session hijacking.

Impact

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N) accurately reflects the limited but concrete confidentiality impact: network-reachable, trivially exploitable by any registered user, no special conditions required. Real-world risk is moderate: the disclosed fields (email, username, privilege flags) are meaningful intelligence for account enumeration, targeted phishing, and privilege-mapping - knowing which accounts have isAdmin or canStream is useful for privilege escalation planning. No EPSS data was provided in the intelligence package, but the low barrier (any authenticated user, single API call) suggests exploitation is mechanically trivial once an attacker has any account. No CISA KEV listing and no public exploit are noted; the issue is straightforward and reproducible from the advisory description alone. The absence of a patch at advisory time is the most acute risk factor - defenders cannot remediate through a vendor update and must rely on compensating controls.

Exploit ScenarioDerived

An attacker registers a free account on a target AVideo instance, then iterates through video IDs via the APIName=video API endpoint. Each response includes the owner's email address, username, and privilege flags (isAdmin, canUpload, canStream), allowing the attacker to build a complete map of admin accounts and their email addresses for follow-on phishing or credential-stuffing campaigns. No special tooling is required beyond authenticated HTTP requests; the vulnerability is mechanically trivial to exploit.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 10, 2026

Incomplete authorization logic in AVideo's video API endpoint exposes private user account fields to any authenticated low-privilege user. The API::get_api_video() method calls removeSensitiveUserFields() only when the caller is a guest or lacks a valid API secret, but never compares the authenticated caller's user ID against the video row's users_id column. Any account holder can therefore request another user's video via APIName=video and receive the owner's email address, account name, isAdmin, canUpload, and canStream flags - data that should be restricted to the owner or callers with a valid API secret. No patch was available at the time of advisory publication; no public exploit has been identified at time of analysis.

RemediationAI

No vendor-released patched version was identified at time of analysis; organizations should monitor https://github.com/WWBN/AVideo/security/advisories/GHSA-qwp4-vh4w-2fh9 for an upstream fix. As an interim compensating control, restrict account registration to prevent untrusted parties from obtaining authenticated sessions, since exploitation requires a low-privilege account. Operators running AVideo in an internal-only context should enforce network-layer controls (firewall, VPN) to limit who can reach the API endpoint, reducing the effective attack surface to trusted users. Administrators should also audit which accounts currently exist, revoke unused or guest accounts, and treat any previously disclosed email or privilege-flag data as potentially enumerated. A code-level patch requires modifying API::get_api_video() to call removeSensitiveUserFields() whenever User::getId() does not match the row's users_id, regardless of authentication state.

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 an open-source self-hosted video platform maintained by WWBN. The root cause (CWE-359, Exposure of Private Personal Information to an Unauthorized Actor) lies in the API layer: the video response SQL joins the video owner's user record into each row, including sensitive columns. The sanitization gate in API::get_api_video() is a binary guest/authenticated check, not an ownership check - it strips sensitive fields for unauthenticated guests and callers without an API secret, but any authenticated session bypasses stripping regardless of whether the requester owns the video. The missing assertion is User::getId() === $row['users_id'] or equivalent. The affected code is present through commit c3edcc274c389816d434acadac07ee78eaf330c1 on the master branch as of 2026-08-23.

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 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Network-accessible API requires only a low-privilege account (PR:L); confidentiality impact is partial (email, username, flags); no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/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
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

AVideo through revision c3edcc274c389816d434acadac07ee78eaf330c1 (master, 2026-08-23) incompletely sanitizes sensitive user fields in the APIName=video response. Video rows include columns joined from the video owner's user record, and API::get_api_video() calls removeSensitiveUserFields() only when the caller is neither authenticated nor using a valid API secret; it never compares User::getId() with the row's users_id. As a result, any low-privilege authenticated account can request another user's video and receive the owner's email address, account name (user), and isAdmin, canUpload and canStream flags, which are removed for guests and should be returned only to the owner or to callers with a valid API secret. No patched version was available at the time of the advisory.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Low
self-hosted open-source video platform, niche deployment 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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Medium

Priority Score

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

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

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