CVE-2026-47694 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in WWBN/AVideo. No vendor fix is recorded yet; mitigation options are listed below.
WWBN AVideo: Stored XSS via unescaped Gallery category description
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-47694.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-47694 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
WWBN/AVideoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
AVideo stores category descriptions from user input and later renders category_description as raw HTML in the Gallery view. A user who can create or edit
categories can store JavaScript in a category description, which executes when another user views the affected Gallery/category page.
This is a stored XSS in the category description field, separate from previously fixed XSS issues in video titles or comments.
Details
Source:
objects/categoryAddNew.json.php
$objCat->setDescription($_POST['description']);
Storage setter:
objects/category.php
public function setDescription($description)
{
$this->description = $description;
}
Sink:
plugin/Gallery/view/mainAreaCategory.php
<div id="categoryDescription<?php echo $duid; ?>" style="display: none;"><?php echo $videos[0]['category_description']; ?></div>
The value is rendered without htmlspecialchars(), htmlentities(), HTMLPurifier, or equivalent output encoding.
PoC
Prerequisites:
- AVideo current master / v29.0
- User account with permission to create or edit categories
- Gallery plugin/view enabled
- At least one video assigned to the affected category
Steps:
- Log in as a user who can create or edit categories.
- Create or edit a category.
- Set the category description to:
<img src=x onerror=alert(document.domain)>
- Save the category.
- Assign at least one video to that category.
- Open the Gallery/category page that renders the category section.
- The payload is inserted into the page as raw HTML and JavaScript executes.
Impact
An attacker with category edit permission can execute JavaScript in the browser of users or administrators who view the affected Gallery/category page. This can be used to perform actions as the victim, steal same-origin data accessible to JavaScript, or abuse administrative UI actions if an administrator views the malicious category.
Recommended fix
- Sanitize category descriptions on input with the same HTML policy used for video descriptions, or store plain text only.
- Encode on output:
echo htmlspecialchars($videos[0]['category_description'], ENT_QUOTES, 'UTF-8');
- If limited HTML is intended, run the description through HTMLPurifier before storage or before render.
- Add regression tests for category description rendering in Gallery views.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | WWBN/AVideo | all versions | No fix |
Affected Products
avideowwbnDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for WWBN/AVideo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of WWBN/AVideo has shipped for CVE-2026-47694 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2026-47694 in your dependencies?
Find it across Packagist, including transitive dependencies.