Skip to main content
VulnerabilityPublished

CVE-2026-33479: WWBN AVideo · Code Injection

Affects WWBN AVideoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 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

Organizations should immediately update WWBN AVideo to a version that includes the patch addressing CVE-2026-33479. If immediate patching is not possible, implement the following mitigations: 1) Restrict access to the Gallery plugin's saveSort.json.php endpoint to trusted IP addresses or internal networks to reduce exposure. 2) Harden admin user practices by educating them to avoid visiting untrusted websites while logged into the AVideo admin interface. 3) Modify session cookie settings to use SameSite=Lax or Strict to prevent cookies from being sent in cross-site requests, mitigating CSRF risks. 4) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the vulnerable endpoint, especially those containing suspicious 'sections' parameter values. 5) Monitor server logs for unusual POST requests to the saveSort.json.php endpoint and signs of code execution anomalies. 6) Implement Content Security Policy (CSP) headers to reduce the risk of malicious script execution in browsers. 7) Conduct regular security audits and penetration testing focusing on plugin endpoints and admin interfaces.

Description

WWBN AVideo is an open source video platform. In versions up to and including 26.0, the Gallery plugin's `saveSort.json.php` endpoint passes unsanitized user input from `$_REQUEST['sections']` array values directly into PHP's `eval()` function. While the endpoint is gated behind `User::isAdmin()`, it has no CSRF token validation. Combined with AVideo's explicit `SameSite=None` session cookie configuration, an attacker can exploit this via cross-site request forgery to achieve unauthenticated remote code execution — requiring only that an admin visits an attacker-controlled page. Commit 087dab8841f8bdb54be184105ef19b47c5698fcb contains a patch.

References

Community reviews

Loading reviews…