Skip to main content
VulnerabilityPublished Updated

CVE-2026-33295: WWBN AVideo · Cross-site Scripting

Affects WWBN AVideoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 26.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 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

Upgrade AVideo and wwbn/AVideo to 26.0.

Affected software

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

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

AI-suggested

To mitigate CVE-2026-33295, organizations should immediately upgrade WWBN AVideo to version 26.0 or later, where the vulnerability is fixed by proper escaping of the clean_title field. Until upgrading is possible, administrators should restrict video creation and modification privileges to trusted users only, minimizing the risk of malicious input. Implementing web application firewalls (WAFs) with rules to detect and block suspicious JavaScript injection attempts in video titles can provide temporary protection. Additionally, security teams should audit existing video records for suspicious or malicious content in the clean_title field and sanitize or remove any unsafe entries. Enabling Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources. Regular monitoring of user activity and logs for unusual behavior related to video uploads or modifications is also recommended.

Description

WWBN AVideo is an open source video platform. Prior to version 26.0, WWBN/AVideo contains a stored cross-site scripting vulnerability in the CDN plugin's download buttons component. The `clean_title` field of a video record is interpolated directly into a JavaScript string literal without any escaping, allowing an attacker who can create or modify a video to inject arbitrary JavaScript that executes in the browser of any user who visits the affected download page. Version 26.0 fixes the issue.

References

Community reviews

Loading reviews…