Skip to main content
VulnerabilityPublished

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

Affects WWBN AVideoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 26.0 when convenient.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 4.0 base score
5.3Medium
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.
Patch
Available – fixed in 26.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 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 31 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 this vulnerability, organizations should immediately upgrade WWBN AVideo to version 26.0 or later, where the issue is fixed. In addition to patching, implement strict input validation and sanitization on all user-supplied data, especially URL parameters that influence page rendering. Replace unsafe DOM manipulation methods like innerHTML with safer alternatives such as textContent or DOMPurify to prevent script execution. Configure session cookies with the HttpOnly and Secure flags to prevent JavaScript access and ensure cookies are transmitted only over HTTPS. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts. Conduct regular security audits and penetration testing focused on XSS vulnerabilities. Educate users about the risks of clicking suspicious links and consider implementing multi-factor authentication to reduce the impact of credential theft. Monitor logs for unusual activity that may indicate exploitation attempts.

Description

WWBN AVideo is an open source video platform. In versions 25.0 and below, there is a reflected XSS vulnerability that allows unauthenticated attackers to execute arbitrary JavaScript in a victim's browser. User input from a URL parameter flows through PHP's json_encode() into a JavaScript function that renders it via innerHTML, bypassing encoding and achieving full script execution. The vulnerability is caused by two issues working together: unescaped user input passed to JavaScript (videoNotFound.php), and innerHTML rendering HTML tags as executable DOM (script.js). The attack can be escalated to steal session cookies, take over accounts, phish credentials via injected login forms, spread self-propagating payloads, and compromise admin accounts — all by exploiting the lack of proper input sanitization and cookie security (e.g., missing HttpOnly flag on PHPSESSID). The issue has been fixed in version 26.0.

References

Community reviews

Loading reviews…