Skip to main content
VulnerabilityPublished

CVE-2026-33480: WWBN AVideo · Server-Side Request Forgery (SSRF)

Affects WWBN AVideoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WWBNAVideoAffected
  • <=26.0
Fixed in–
GitHubwwbn/AVideopkg:github/wwbn/AVideoOther threatsAffected
  • <=26.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade WWBN AVideo to a version that includes the patch for CVE-2026-33480 or apply the vendor's patch from commit 75ce8a579a58c9d4c7aafe453fbced002cb8f373.
  2. If patching is not immediately possible, restrict access to the plugin/LiveLinks/proxy.php endpoint via network controls or web application firewall (WAF) rules to trusted users or IP addresses only.
  3. Implement network segmentation to limit the AVideo server's access to sensitive internal resources and cloud metadata endpoints.
  4. Monitor logs for unusual requests to the proxy.php endpoint, especially those containing IPv4-mapped IPv6 addresses or requests targeting internal IP ranges.
  5. Consider disabling or restricting the use of the LiveLinks proxy feature if it is not required.
  6. Employ runtime application self-protection (RASP) or enhanced input validation to detect and block SSRF attempts.
  7. Review cloud environment metadata service access policies and consider using metadata service version 2 (IMDSv2) or equivalent protections to reduce risk from SSRF attacks.
  8. Conduct internal penetration testing to verify that the vulnerability is remediated and that no other SSRF vectors exist.

Description

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 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.

References

Community reviews

Loading reviews…