Cyber Resilience

CVE-2026-33480

SSRF in Wwbn Avideo ≤ 26.0

Public PoCSSRF
Published
23 March 2026
Modified
24 March 2026
Patch / advisory
CVSS Score v3.1 8.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS Score 0.0032 25th percentile
Risk Priority 61 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-33480 is a high-severity SSRF (CWE-918) 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 at the 25th 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-33480 is a server-side request forgery (SSRF) vulnerability affecting WWBN AVideo, an open source video platform, in versions up to and including 26.0. The issue stems from a bypass in the `isSSRFSafeURL()` function, which can be circumvented using IPv4-mapped IPv6 addresses in the format `::ffff:x.x.x.x`. This function is employed by the unauthenticated `plugin/LiveLinks/proxy.php` endpoint to validate URLs prior to fetching them via curl.

Unauthenticated attackers can exploit this vulnerability remotely with low complexity and no user interaction required, as indicated by its CVSS v3.1 base score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) and association with CWE-918 (Server-Side Request Forgery). Successful exploitation allows attackers to access cloud metadata services, internal networks, and localhost services by tricking the proxy endpoint into making unauthorized requests on their behalf.

The GitHub security advisory (GHSA-p3gr-g84w-g8hh) and commit 75ce8a579a58c9d4c7aafe453fbced002cb8f373 detail the patch, which addresses the IPv4-mapped IPv6 bypass in the validation logic. Security practitioners should update to a patched version of AVideo beyond 26.0 and review configurations of the LiveLinks plugin to mitigate exposure.

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, the `isSSRFSafeURL()` function in AVideo can be bypassed using IPv4-mapped IPv6 addresses (`::ffff:x.x.x.x`). The unauthenticated `plugin/LiveLinks/proxy.php` endpoint uses this function to validate URLs before fetching…

more

them with curl, but the IPv4-mapped IPv6 prefix passes all checks, allowing an attacker to access cloud metadata services, internal networks, and localhost services. Commit 75ce8a579a58c9d4c7aafe453fbced002cb8f373 contains a patch.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33351Same product: Wwbn Avideo
CVE-2026-39370Same product: Wwbn Avideo
CVE-2026-33294Same product: Wwbn Avideo
CVE-2026-33502Same product: Wwbn Avideo
CVE-2026-33039Same product: Wwbn Avideo
CVE-2026-33766Same product: Wwbn Avideo
CVE-2026-41055Same product: Wwbn Avideo
CVE-2026-34740Same product: Wwbn Avideo
CVE-2026-39368Same product: Wwbn Avideo
CVE-2026-41060Same 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)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.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.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

PR.PS-06 partial match
prevents

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

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.

prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

References