VulnerabilityPublished 23 Mar 2026

CVE-2026-33513: WWBN AVideo · Path Traversal

Affects WWBN AVideoSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.6 High.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
WWBNAVideo	Affected <=26.0	Fixed in–
GitHubwwbn/AVideo`pkg:github/wwbn/AVideo`Other threats	Affected <=26.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since no official patches are currently available, organizations should implement immediate compensating controls. First, restrict access to the vulnerable API endpoint (`APIName=locale`) using network-level controls such as firewalls, IP whitelisting, or web application firewalls (WAFs) to block unauthenticated external access. Second, implement input validation and sanitization on the server side to prevent path traversal characters (e.g., `../`) from being processed in include paths. Third, review and harden file upload mechanisms and directory permissions to prevent attackers from placing arbitrary PHP files in the web root or other accessible directories. Fourth, monitor web server logs and application logs for suspicious requests attempting path traversal or unusual file inclusions. Fifth, consider isolating the AVideo application in a container or sandbox environment to limit the blast radius of potential exploitation. Finally, maintain regular backups and prepare incident response plans in case of compromise. Organizations should track WWBN announcements for forthcoming patches and apply them promptly once released.

Description

CVE-2026-33513 is a high-severity path traversal vulnerability in WWBN AVideo versions up to 26.0. An unauthenticated API endpoint improperly concatenates user input into an include path without validation, allowing attackers to traverse directories and include arbitrary PHP files within the web root. This can lead to file disclosure and limited code execution of existing PHP files. If an attacker can upload or control PHP files elsewhere in the directory tree, this vulnerability can escalate to full remote code execution (RCE). No patches are currently available, and exploitation requires no authentication or user interaction. The vulnerability poses significant risk to organizations using AVideo for video hosting and streaming, especially those with publicly accessible instances. Immediate mitigations include restricting access to the vulnerable API, implementing input validation, and monitoring for suspicious file access patterns.

Impact

The impact of CVE-2026-33513 is significant for organizations deploying WWBN AVideo as it allows unauthenticated attackers to read arbitrary files within the web root, potentially exposing sensitive configuration files, credentials, or user data. More critically, the vulnerability can lead to remote code execution if attackers can upload or otherwise control PHP files on the server, enabling full system compromise. This can result in data breaches, service disruption, defacement, or use of the compromised server as a pivot point for further attacks. Given that AVideo is often used for video hosting and streaming, exploitation could disrupt media services, damage reputation, and lead to regulatory or compliance issues. The lack of available patches increases the urgency for mitigation. Organizations with publicly accessible AVideo instances are at highest risk, especially if other vulnerabilities or misconfigurations allow file uploads or write access. The vulnerability affects confidentiality, integrity, and availability, making it a critical concern for affected deployments worldwide.

Summary

CVE-2026-33513 affects WWBN AVideo, an open-source video platform, in versions up to and including 26.0. The vulnerability arises from an unauthenticated API endpoint identified by the parameter `APIName=locale`, which concatenates user-supplied input directly into a PHP include path without performing canonicalization or enforcing a whitelist. This improper limitation of pathname (CWE-22) allows attackers to perform path traversal attacks, enabling them to include arbitrary PHP files located anywhere under the web root directory. In practical tests, attackers have confirmed the ability to disclose sensitive files and execute code contained within existing PHP files, such as `view/about.php`. The vulnerability can escalate to remote code execution if the attacker can place or control PHP files elsewhere in the directory tree, for example via other upload functionalities or misconfigurations. The vulnerability is exploitable remotely, requires no authentication or user interaction, and impacts confidentiality, integrity, and availability of affected systems. As of the publication date, no official patches or updates have been released by WWBN to address this issue. The CVSS v3.1 base score is 8.6, reflecting its high severity and ease of exploitation. The vulnerability is also associated with CWE-98, indicating improper control of filename for include/require statements in PHP.

CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-98Improper Control of Filename for Include/Require Statement in PHP Program (Remote File Include) (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Vulnerable Dependency Management (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.3 (opens in a new tab)
V12.3.6 (opens in a new tab)
V14.2.3 (opens in a new tab)
Attack patterns
PHP Remote File Inclusion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/WWBN/AVideo/security/advisories/GHSA-8fw8-q79c-fp9m (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Mar 2026, 20:40 UTC

WeaknessesCWE-22, CWE-98

Technical details

References

Community reviews

Related threats