Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:LSummary
CVE-2026-33513 is a high-severity Path Traversal (CWE-22) vulnerability in Wwbn Avideo. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 49% of CVEs by exploit likelihood; 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 AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — 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-33513 is a path traversal vulnerability (CWE-22, CWE-98) in WWBN AVideo, an open-source video platform, affecting versions up to and including 26.0. The issue stems from an unauthenticated API endpoint (`APIName=locale`) that concatenates user-supplied input directly into a PHP `include` path without canonicalization or whitelisting. This allows traversal outside intended directories, enabling the inclusion and execution of arbitrary PHP files under the web root.
Unauthenticated remote attackers can exploit this vulnerability over the network with low attack complexity, no privileges, no user interaction, and unchanged scope (CVSSv3.1 score: 8.6; AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L). Exploitation results in confirmed file disclosure and execution of existing PHP content, such as `view/about.php`. It can escalate to remote code execution (RCE) if the attacker can place or control a PHP file elsewhere in the traversable tree under the web root.
The GitHub security advisory (GHSA-8fw8-q79c-fp9m) states that, as of the CVE publication on 2026-03-23, no patched versions of AVideo are available. Security practitioners should monitor the repository for updates while applying workarounds like disabling the vulnerable endpoint if feasible.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-14480
Vulnerability Data
WWBN AVideo is an open source video platform. In versions up to and including 26.0, an unauthenticated API endpoint (`APIName=locale`) concatenates user input into an `include` path with no canonicalization or whitelist. Path traversal is accepted, so arbitrary PHP files…
more
under the web root can be included. In our test this yielded confirmed file disclosure and code execution of existing PHP content (e.g., `view/about.php`), and it *can* escalate to RCE if an attacker can place or control a PHP file elsewhere in the tree. As of time of publication, no patched versions are available.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Developer testing and static analysis can discover missing filename restrictions before deployment.
Input validation directly neutralizes special path elements before pathname construction occurs.
Information-flow rules can block the loading of external or unauthorized files into the PHP process.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.
Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
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.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.