Skip to main content

Avideo CVE-2026-33647

| EUVDEUVD-2026-14482 HIGH
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-03-23 GitHub_M GHSA-wxjw-phj6-g75w
8.8
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

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

  1. Access
    Authenticate to AVideo platform
  2. Delivery
    Upload polyglot JPEG/PHP file with .php extension
  3. Exploit
    MIME validation passes, file saved as executable
  4. Execution
    Access uploaded file via web
  5. Impact
    Execute arbitrary PHP code as web server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK

2 techniques across 2 tactics: Command and Control, 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 (PR:L) with upload permission to AVideo image gallery in versions ≤26.0. Attacker uploads polyglot file (valid JPEG magic bytes + PHP code) with .php extension. File saved in web-accessible directory despite MIME validation, enabling RCE.

Impact

This vulnerability represents a critical real-world risk with a CVSS score of 8.8 (High). The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates network-based exploitation with low attack complexity requiring only low-level privileges (authenticated user) and no user interaction, leading to complete compromise of confidentiality, integrity, and availability. The technical impact is maximal since successful exploitation grants Remote Code Execution capabilities. The vulnerability requires authentication (PR:L), which provides some defense in depth, but once an attacker has low-privileged access (potentially through default credentials or social engineering), exploitation is straightforward. The availability of a GitHub Security Advisory and specific commit patch indicates this vulnerability is well-documented and understood by attackers. While EPSS data and KEV status are not provided in the intelligence sources, the combination of public disclosure, patch availability, clear exploitation path, and RCE impact make this a high-priority issue requiring immediate attention. The attack is automatable once credentials are obtained, and exploitation would likely result in full system compromise.

Exploit ScenarioDerived

An authenticated attacker with low-level privileges creates a polyglot file by prepending valid JPEG magic bytes and header to PHP code containing a web shell, then names the file with a .php extension (e.g., shell.php). The attacker uploads this file through the AVideo ImageGallery feature, which validates the JPEG MIME type based on the initial bytes but saves the file with the attacker-controlled .php extension in a web-accessible directory. The attacker then requests the uploaded PHP file via HTTP, causing the web server to execute the embedded PHP code and granting the attacker a remote shell with the privileges of the web server process, enabling full system compromise.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.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 – Mar 23, 2026

WWBN AVideo versions up to and including 26.0 contain a critical file upload vulnerability in the ImageGallery::saveFile() method that allows authenticated attackers to upload polyglot files (JPEG with embedded PHP code) and achieve Remote Code Execution. The vulnerability exploits a mismatch between MIME type validation (which checks file content) and filename extension handling (which trusts user input), allowing attackers to bypass security controls and execute arbitrary code on the server. A patch is available in commit 345a8d3ece0ad1e1b71a704c1579cbf885d8f3ae, and the issue has been publicly disclosed via GitHub Security Advisory GHSA-wxjw-phj6-g75w.

RemediationAI

Apply the security patch available in commit 345a8d3ece0ad1e1b71a704c1579cbf885d8f3ae from the WWBN AVideo GitHub repository (https://github.com/WWBN/AVideo/commit/345a8d3ece0ad1e1b71a704c1579cbf885d8f3ae). Review the full security advisory at https://github.com/WWBN/AVideo/security/advisories/GHSA-wxjw-phj6-g75w for additional context and upgrading to the next stable release that incorporates this fix. Until patching is complete, implement compensating controls including restricting file upload functionality to highly trusted administrators only, implementing strict file extension allowlists at the web server or WAF level to block PHP and other executable extensions in upload directories, ensuring upload directories have execute permissions disabled at the filesystem level, and monitoring for suspicious file uploads with polyglot characteristics. Consider temporarily disabling the ImageGallery upload feature if not business-critical until the patch can be applied.

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:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*), an open-source video platform built on PHP. The root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type), which occurs when the ImageGallery::saveFile() method validates file content using PHP's finfo library for MIME type detection but fails to validate the file extension against an allowlist before saving. The method derives the saved filename extension directly from the user-supplied original filename, creating a logic flaw where polyglot files can pass content validation while retaining dangerous executable extensions. This is a classic example of incomplete input validation where different components of the security control (content check vs. filename check) operate independently without proper coordination.

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.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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
High

DescriptionGitHub Advisory

WWBN AVideo is an open source video platform. In versions up to and including 26.0, the ImageGallery::saveFile() method validates uploaded file content using finfo MIME type detection but derives the saved filename extension from the user-supplied original filename without an allowlist check. An attacker can upload a polyglot file (valid JPEG magic bytes followed by PHP code) with a .php extension. The MIME check passes, but the file is saved as an executable .php file in a web-accessible directory, achieving Remote Code Execution. Commit 345a8d3ece0ad1e1b71a704c1579cbf885d8f3ae contains a patch.

Executive ViewAI

Why It Matters

WWBN AVideo installations (versions ≤26.0) are vulnerable to remote code execution through authenticated file upload attacks, potentially allowing attackers to gain complete control of affected servers. Any organization running this software faces immediate risk of data breach, service disruption, and system compromise if the vulnerability is exploited.

Business Impact: Severe
Compensating Controls

Implement Web Application Firewall (WAF) rules to block file uploads with polyglot characteristics or mismatched MIME types and extensions; restrict image gallery upload functionality to administrative users only; disable the ImageGallery feature entirely if not business-critical; enforce strict input validation at the application layer requiring file content re-validation; isolate WWBN AVideo instances on segmented networks with egress filtering to limit lateral movement if compromise occurs; implement real-time file integrity monitoring on upload directories.

Threat Intelligence Overview

EPSS Score
0.2%
Top 57% 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.2%
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
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

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

Attack Technique

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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