CVE-2026-47694: WWBN AVideo: Stored XSS via unescaped Gallery category description
Summary
AVideo stores category descriptions from user input and later renders categorydescription 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
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]['categorydescription']; ?></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:
1. Log in as a user who can create or edit categories. 2. Create or edit a category. 3. Set the category description to: <img src=x onerror=alert(document.domain)> 4. Save the category. 5. Assign at least one video to that category. 6. Open the Gallery/category page that renders the category section. 7. 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:
php echo htmlspecialchars($videos[0]['categorydescription'], ENTQUOTES, '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.
Other sources
WWBN AVideo is an open source video platform. In 29.0 and earlier, AVideo stores category descriptions from user input and later renders categorydescription 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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
AVideoto a version that resolves this vulnerability.Fixed in 29.0 - Configuration
Update the category description rendering in `plugin/Gallery/view/mainAreaCategory.php` to output-encode the value using `htmlspecialchars(..., ENT_QUOTES, 'UTF-8')` instead of echoing raw HTML/JS.
Gallery view (plugin/Gallery/view/mainAreaCategory.php) category_description output encoding = echo htmlspecialchars($videos[0]['category_description'], ENT_QUOTES, 'UTF-8'); - Configuration
Modify `objects/category.php` in `setDescription($description)` to sanitize/encode `category_description` on input using the same HTML policy as video descriptions. If limited HTML is intended, use HTMLPurifier before storage or before render; otherwise store plain text only.
Category storage/input (objects/category.php / setDescription) category description sanitization/encoding policy = Encode with same HTML policy as video descriptions, or store plain text only; if limited HTML is intended, run through HTMLPurifier before storage or before render. - Compensating control
Assign at least one video to any category that contains category descriptions (as part of verification/reproduction steps) so the affected Gallery/category page renders the category description and the fixed rendering behavior can be validated.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-47694?
The severity of CVE-2026-47694 is medium with a CVSS score of 5.4.
How do I fix CVE-2026-47694?
To fix CVE-2026-47694, ensure that category descriptions are properly sanitized to prevent the execution of unescaped JavaScript.
What software is affected by CVE-2026-47694?
CVE-2026-47694 affects WWBN AVideo versions 29.0 and earlier.
What type of vulnerability is CVE-2026-47694?
CVE-2026-47694 is classified as a stored cross-site scripting (XSS) vulnerability.
Who can exploit CVE-2026-47694?
Any user with the ability to create or edit categories in WWBN AVideo can exploit CVE-2026-47694 by injecting JavaScript into category descriptions.