Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-c8h8-vq34-9fw2

MEDIUM

WWBN AVideo: Stored XSS via unescaped Gallery category description

Also known asCVE-2026-47694
Published
Jun 4, 2026
Updated
Jun 18, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk6th percentile0.00%
0.00%0.22%0.44%0.66%0.0%0.2%0.2%Jun 26Jul 26Jul 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
🐘WWBN/AVideo

Real-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:

  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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐘PackagistWWBN/AVideoall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for WWBN/AVideo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of WWBN/AVideo has shipped for GHSA-c8h8-vq34-9fw2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-c8h8-vq34-9fw2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c8h8-vq34-9fw2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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` ```php $objCat->setDescription($_POST['description']); Storage setter: objects/category.p
O3 Security · Impact-Aware SCA

Is GHSA-c8h8-vq34-9fw2 in your dependencies?

O3 detects GHSA-c8h8-vq34-9fw2 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.