Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2022-30547 is a critical-severity Path Traversal (CWE-22) vulnerability in Wwbn Avideo. Its CVSS base score is 9.9 (Critical).
Operationally, ranked in the top 0.9% 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 SI-10 (Information Input Validation) and AC-6 (Least Privilege) — 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.
A directory traversal vulnerability exists in the unzipDirectory functionality of WWBN AVideo version 11.6 and the development master commit 3f7c0364. Tracked as CVE-2022-30547 and assigned CWE-22, the flaw allows a specially crafted HTTP request to trigger arbitrary command execution. The issue carries a CVSS 3.1 score of 9.9, reflecting network attack vector, low attack complexity, low privileges required, and impacts across confidentiality, integrity, and availability with a scope change.
An authenticated attacker can send a crafted HTTP request to the affected unzipDirectory component and achieve arbitrary command execution on the server. The attack requires no user interaction and can be performed remotely over the network.
Public references include a Talos Intelligence vulnerability report (TALOS-2022-1547) and database update scripts hosted in the AVideo GitHub repository that address version 12.0.
EPSS for the CVE rose from low values after disclosure to a peak of 0.3369 on 2025-12-11 before receding to the current 0.2074, indicating that exploitation interest emerged well after the initial publication.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-52406
Vulnerability Data
A directory traversal vulnerability exists in the unzipDirectory functionality of WWBN AVideo 11.6 and dev master commit 3f7c0364. A specially-crafted HTTP request can lead to arbitrary command execution. An attacker can send an HTTP request to trigger this vulnerability.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly blocks the crafted HTTP request by validating path and filename inputs to unzipDirectory before traversal sequences can be processed.
Limits the privileges of authenticated users so that even successful traversal cannot result in arbitrary command execution outside the intended scope.
Requires timely application of the vendor-supplied patches (v12.0 database scripts) that remediate the directory traversal flaw in unzipDirectory.
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.