Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-33351 is a critical-severity SSRF (CWE-918) vulnerability in Wwbn Avideo. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 36th 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-4 (Information Flow 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-33351 is a Server-Side Request Forgery (SSRF) vulnerability (CWE-918) in the open source video platform WWBN AVideo, affecting versions prior to 26.0. The flaw exists in the file `plugin/Live/standAloneFiles/saveDVR.json.php` when the AVideo Live plugin is deployed in standalone mode, its intended configuration. There, the `$_REQUEST['webSiteRootURL']` parameter is used directly to construct a URL fetched server-side via `file_get_contents()`, with no authentication, origin validation, or URL allowlisting performed. The vulnerability carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
An unauthenticated attacker with network access can exploit this by sending a crafted HTTP request to the vulnerable endpoint, supplying a malicious `webSiteRootURL`. This causes the server to fetch arbitrary URLs, potentially allowing access to internal network resources, metadata services, or cloud infrastructure unreachable from the internet. Successful exploitation leads to high confidentiality and integrity impacts, such as data exfiltration or further compromise via SSRF chaining, with low attack complexity and no user interaction required.
AVideo version 26.0 addresses the issue with a patch. Security practitioners should upgrade to this version immediately. Further details, including the fixing commit, are documented in the GitHub security advisory at GHSA-5f7v-4f6g-74rj and commit d0c54960389eeb85e76caed5a257ae90e6a739f2.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-20073
Vulnerability Data
WWBN AVideo is an open source video platform. Prior to version 26.0, a Server-Side Request Forgery (SSRF) vulnerability exists in `plugin/Live/standAloneFiles/saveDVR.json.php`. When the AVideo Live plugin is deployed in standalone mode (the intended configuration for this file), the `$_REQUEST['webSiteRootURL']` parameter…
more
is used directly to construct a URL that is fetched server-side via `file_get_contents()`. No authentication, origin validation, or URL allowlisting is performed. Version 26.0 contains a patch for the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.5.3V5.3.2V10.4.7
Mitigating Controls (NIST 800-53 r5) AI
Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.
Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.
Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.
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 development practices directly include input validation and destination allow-listing that prevent SSRF.
Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.
Vulnerability identification processes can discover and record SSRF flaws in web applications.
Network segmentation and egress controls can limit the damage from successful SSRF requests.
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.
Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.