Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-33681 is a high-severity Path Traversal (CWE-22) vulnerability in Wwbn Avideo. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 40th 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 AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — 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-33681 is a path traversal vulnerability (CWE-22) affecting WWBN AVideo, an open source video platform, in versions up to and including 26.0. The issue resides in the `objects/pluginRunDatabaseScript.json.php` endpoint, which accepts a `name` parameter via POST and passes it unsanitized to the `Plugin::getDatabaseFileName()` function. This flaw enables attackers to navigate outside the intended plugin directory and access arbitrary `install/install.sql` files on the filesystem, executing their contents as raw SQL queries directly against the application's database.
Exploitation requires high privileges, as indicated by the CVSS v3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). An authenticated administrator can directly trigger the endpoint to achieve SQL injection-like effects by supplying a crafted `name` parameter with traversal sequences (e.g., `../`). Alternatively, an unauthenticated attacker could exploit this via cross-site request forgery (CSRF) if targeting an admin user, potentially leading to unauthorized database modifications, data exfiltration, or destruction depending on the contents of accessible `install.sql` files.
The vulnerability is addressed in commit 81b591c509835505cb9f298aa1162ac64c4152cb, available on the WWBN/AVideo GitHub repository, which patches the path traversal issue. Additional details and mitigation guidance are provided in the GitHub Security Advisory GHSA-3hwv-x8g3-9qpr. Security practitioners should urge AVideo users to update to a patched version beyond 26.0 and review access controls for admin endpoints to prevent CSRF abuse.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-14492
Vulnerability Data
WWBN AVideo is an open source video platform. In versions up to and including 26.0, the `objects/pluginRunDatabaseScript.json.php` endpoint accepts a `name` parameter via POST and passes it to `Plugin::getDatabaseFileName()` without any path traversal sanitization. This allows an authenticated admin (or…
more
an attacker via CSRF) to traverse outside the plugin directory and execute the contents of any `install/install.sql` file on the filesystem as raw SQL queries against the application database. Commit 81b591c509835505cb9f298aa1162ac64c4152cb contains a patch.
- 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.
Input validation directly neutralizes special path elements before pathname construction occurs.
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.
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.
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.