Skip to content

WWBN AVideo: Stored XSS via unescaped Gallery category description

Moderate severity GitHub Reviewed Published May 19, 2026 in WWBN/AVideo • Updated Jun 4, 2026

Package

composer WWBN/AVideo (Composer)

Affected versions

<= 29.0

Patched versions

None

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:

  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)>
  1. Save the category.
  2. Assign at least one video to that category.
  3. Open the Gallery/category page that renders the category section.
  4. 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.

References

@DanielnetoDotCom DanielnetoDotCom published to WWBN/AVideo May 19, 2026
Published by the National Vulnerability Database May 29, 2026
Published to the GitHub Advisory Database Jun 4, 2026
Reviewed Jun 4, 2026
Last updated Jun 4, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(14th percentile)

Weaknesses

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Learn more on MITRE.

CVE ID

CVE-2026-47694

GHSA ID

GHSA-c8h8-vq34-9fw2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.