Skip to main content

Avideo EUVDEUVD-2026-14490

| CVE-2026-33651 HIGH
SQL Injection (CWE-89)
2026-03-23 GitHub_M GHSA-pvw4-p2jm-chjm
8.1
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

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

  1. Access
    Authenticate as low-privilege user
  2. Delivery
    Send crafted live_schedule_id parameter
  3. Exploit
    Bypass intval() sanitization in intermediate functions
  4. Execution
    Inject SQL into LIKE clause
  5. Persist
    Execute time-based blind SQL injection query
  6. Impact
    Extract sensitive database contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Authenticated user access required. WWBN AVideo versions up to 26.0, specifically the remindMe.json.php endpoint with live_schedule_id parameter. Attacker must be authenticated to exploit time-based blind SQL injection via unsanitized parameter concatenation in SQL LIKE clause.

Impact

This vulnerability presents a significant real-world risk despite requiring low-privilege authentication (PR:L). The CVSS score of 8.1 (High) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N indicates network-exploitable attacks with low complexity requiring only basic user credentials. The high confidentiality and integrity impact means attackers can both steal and potentially modify database contents. While no EPSS score or KEV status is provided in the available data, the availability of a GitHub security advisory and specific patch commit suggests the vulnerability has been publicly disclosed with technical details that could facilitate exploitation. The time-based blind SQL injection technique is well-documented and automatable, making this exploitable by moderately skilled attackers once they obtain any valid user account. Organizations running AVideo should prioritize patching, especially if the platform is exposed to untrusted authenticated users.

Exploit ScenarioDerived

An attacker creates a standard user account on an AVideo platform or obtains credentials through social engineering or credential stuffing. They then craft malicious HTTP requests to the remindMe.json.php endpoint with specially crafted live_schedule_id parameters containing SQL injection payloads designed for time-based blind extraction, such as using SLEEP() or BENCHMARK() functions. By measuring response times across multiple requests with different payloads, the attacker systematically extracts administrator credentials, API keys, user personal information, and video access records from the database, enabling account takeover and unauthorized access to private content.

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

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

Alert me

AnalysisAIv1 – Mar 23, 2026

SQL injection in WWBN AVideo up to version 26.0 allows authenticated users to extract arbitrary database contents through time-based blind SQL injection via the remindMe.json.php endpoint. The vulnerability stems from insufficient input sanitization of the live_schedule_id parameter, which is concatenated directly into a SQL LIKE clause despite partial validation in intermediate functions. No patch is currently available.

Earlier versions of this analysis (1)
v1 Mar 23, 2026 - 19:00 CVSS 8.1

A SQL injection vulnerability exists in WWBN AVideo, an open source video platform, affecting versions up to and including 26.0. Any authenticated user can exploit the remindMe.json.php endpoint to perform time-based blind SQL injection and extract arbitrary database contents including credentials, user data, and other sensitive information. A patch is available in commit 75d45780728294ededa1e3f842f95295d3e7d144, and GitHub has published a security advisory (GHSA-pvw4-p2jm-chjm).

RemediationAI

Apply the patch provided in commit 75d45780728294ededa1e3f842f95295d3e7d144 available at https://github.com/WWBN/AVideo/commit/75d45780728294ededa1e3f842f95295d3e7d144, which addresses the SQL injection by properly sanitizing the live_schedule_id parameter before database operations. Organizations should upgrade to a patched version beyond 26.0 that incorporates this commit. Review the GitHub security advisory at https://github.com/WWBN/AVideo/security/advisories/GHSA-pvw4-p2jm-chjm for additional guidance from the vendor. As an interim mitigation while patching, consider implementing web application firewall rules to detect and block SQL injection attempts targeting the remindMe.json.php endpoint, restrict database user permissions to minimize potential data exposure, and audit user accounts to ensure only trusted users have authentication credentials. Monitor database query logs for suspicious LIKE clause patterns or unusually slow queries that may indicate exploitation attempts.

Affected VersionsENISA

AVideo ≤ 26.0

Affected Packages

composer wwbn/avideo no fix
euvd avideo no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in composer, euvd

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

Technical ContextAI · show details

This vulnerability affects WWBN AVideo (CPE: cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*), a PHP-based open source video streaming and management platform. The root cause is CWE-89 (SQL Injection), specifically occurring when the live_schedule_id parameter from user requests passes through multiple functions including Live_schedule constructor and getUsers_idOrCompany without proper sanitization. Although intermediate functions apply intval() for type casting, they operate on local copies within ObjectYPT::getFromDb(), leaving the original tainted variable intact. This tainted input eventually reaches Scheduler_commands::getAllActiveOrToRepeat() where it is directly concatenated into a SQL LIKE clause, enabling time-based blind SQL injection attacks that allow attackers to infer database contents through response timing differentials.

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

GitHub Advisory PRIMARY 8.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionGitHub Advisory

WWBN AVideo is an open source video platform. In versions up to and including 26.0, the remindMe.json.php endpoint passes $_REQUEST['live_schedule_id'] through multiple functions without sanitization until it reaches Scheduler_commands::getAllActiveOrToRepeat(), which directly concatenates it into a SQL LIKE clause. Although intermediate functions (new Live_schedule(), getUsers_idOrCompany()) apply intval() internally, they do so on local copies within ObjectYPT::getFromDb(), leaving the original tainted variable unchanged. Any authenticated user can perform time-based blind SQL injection to extract arbitrary database contents. Commit 75d45780728294ededa1e3f842f95295d3e7d144 contains a patch.

Executive ViewAI

Why It Matters

A high-severity SQL injection vulnerability in WWBN AVideo allows authenticated users to extract sensitive data including credentials and user information from your database. Any organization running AVideo versions 26.0 or earlier faces immediate risk of data breach and unauthorized access to customer and operational data.

Business Impact: High
Compensating Controls

Until patching is complete: (1) Implement WAF rules to block requests to remindMe.json.php endpoint; (2) Restrict network access to AVideo instances using IP whitelisting or VPN; (3) Disable the remindMe functionality if not operationally critical; (4) Implement rate limiting and monitoring on the vulnerable endpoint; (5) Enforce multi-factor authentication for all user accounts to limit lateral movement if credentials are compromised.

Threat Intelligence Overview

EPSS Score
0.0%
Top 93% exploitable
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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.0%
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
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

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