Cyber Resilience

CVE-2026-33354

Path Traversal in Wwbn Avideo ≤ 26.0

Public PoCPath Traversal
Published
23 March 2026
Modified
24 March 2026
Patch / advisory
CVSS Score v3.1 7.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
EPSS Score 0.0025 17th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-33354 is a high-severity External Control of File Name or Path (CWE-73) vulnerability in Wwbn Avideo. Its CVSS base score is 7.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-33354 is a vulnerability in WWBN AVideo, an open source video platform, affecting versions up to and including 26.0. The issue lies in the `POST /objects/aVideoEncoder.json.php` endpoint, which processes a requester-controlled `chunkFile` parameter intended for staged upload chunks. Rather than restricting paths to trusted server-generated chunk locations, the endpoint accepts arbitrary local filesystem paths that pass the `isValidURLOrPath()` helper function. This function permits files under broad server directories such as `/var/www/`, the application root, cache, tmp, and `videos`, while only rejecting `.php` files.

An authenticated uploader editing their own video can exploit this flaw to achieve arbitrary local file reads. By specifying a target path in the `chunkFile` parameter, the endpoint copies the attacker-chosen local file into the attacker's public video storage path, after which it becomes downloadable over HTTP. The vulnerability carries a CVSS v3.1 base score of 7.6 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L) and maps to CWE-73.

Mitigation is addressed in commit 59bbd601a3f65a5b18c1d9e4eb11471c0a59214f on the AVideo GitHub repository, which patches the issue. Additional details are available in the GitHub security advisory GHSA-4jw9-5hrc-m4j6.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

WWBN AVideo is an open source video platform. In versions up to and including 26.0, `POST /objects/aVideoEncoder.json.php` accepts a requester-controlled `chunkFile` parameter intended for staged upload chunks. Instead of restricting that path to trusted server-generated chunk locations, the endpoint accepts…

more

arbitrary local filesystem paths that pass `isValidURLOrPath()`. That helper allows files under broad server directories including `/var/www/`, the application root, cache, tmp, and `videos`, only rejecting `.php` files. For an authenticated uploader editing their own video, this becomes an arbitrary local file read. The endpoint copies the attacker-chosen local file into the attacker's public video storage path, after which it can be downloaded over HTTP. Commit 59bbd601a3f65a5b18c1d9e4eb11471c0a59214f contains a patch for the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1574.007 Path Interception by PATH Environment Variable Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-47862Same product: Wwbn Avideo
CVE-2023-49738Same product: Wwbn Avideo
CVE-2023-47171Same product: Wwbn Avideo
CVE-2023-49864Same product: Wwbn Avideo
CVE-2023-49863Same product: Wwbn Avideo
CVE-2023-49862Same product: Wwbn Avideo
CVE-2026-39370Same product: Wwbn Avideo
CVE-2026-33485Same product: Wwbn Avideo
CVE-2026-33039Same product: Wwbn Avideo
CVE-2026-41055Same product: Wwbn Avideo

Affected Assets

wwbn
avideo
≤ 26.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly rejects or sanitizes untrusted path strings before they reach filesystem operations.

Enforces authorization checks on the actual resource accessed, blocking unauthorized files even when a malicious path is supplied.

Least-privilege limits the set of files or directories any subject can affect, shrinking the blast radius of a path-control flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices include input validation and path sanitization that eliminate this weakness.

PR.AA-05 mostly match
prevents

Least-privilege file authorization directly limits damage from externally controlled paths.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect path-traversal issues but does not itself implement preventive controls.

prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent external file/path manipulation.

prevents

Application security requirements explicitly call for controls against untrusted input influencing file operations.

prevents

Secure architecture principles discourage unsafe path construction but do not prescribe concrete file-name controls.

prevents

Secure coding standards require canonicalization, allow-listing, and bounds checks on file paths, directly eliminating CWE-73.

mitigates

Information access restriction limits which files can be reached, indirectly reducing impact of path manipulation.

References