Skip to main content
VulnerabilityPublished

CVE-2026-33647: WWBN AVideo · Unrestricted File Upload

Affects WWBN AVideoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 29 Oct 2026, 19:04 UTC

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

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 29 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 apply the official patch referenced by commit 345a8d3ece0ad1e1b71a704c1579cbf885d8f3ae to all affected AVideo installations.
  2. Implement strict server-side validation of uploaded file extensions against a whitelist of allowed types, ensuring the extension matches the MIME type.
  3. Sanitize and normalize filenames before saving to prevent injection of dangerous extensions.
  4. Configure the web server to disallow execution of scripts in upload directories, for example, by disabling PHP execution in those folders via .htaccess or server configuration.
  5. Employ Content Security Policy (CSP) headers and other web application firewalls (WAF) to detect and block suspicious upload attempts.
  6. Monitor logs for unusual file uploads or access patterns to detect exploitation attempts early.
  7. Educate developers and administrators on secure file upload handling best practices to prevent similar vulnerabilities.
  8. Consider isolating the upload directory in a sandboxed environment with minimal privileges to limit impact if exploitation occurs.

Description

CVE-2026-33647 is a high-severity vulnerability in WWBN AVideo versions up to 26.0 that allows remote code execution via unrestricted upload of a file with a dangerous extension. The vulnerability arises because the application validates uploaded file content using MIME type detection but does not enforce an allowlist on the file extension derived from the user-supplied filename. Attackers can upload a crafted polyglot file containing valid JPEG headers followed by embedded PHP code with a . php extension. Since the MIME check passes, the file is saved as an executable PHP script in a web-accessible directory, enabling execution of arbitrary code on the server. No user interaction is required beyond file upload, and the exploit requires low privileges. A patch addressing this issue has been committed. Organizations running vulnerable versions should apply the patch immediately and implement stricter file extension validation to prevent exploitation.

References

Community reviews

Loading reviews…