Quick answers
- Is CVE-2026-47694 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47694 being exploited in the wild.
- How severe is CVE-2026-47694?
- Medium severity, with a CVSS score of 5.4, published 29 May 2026.
- Which products and versions are affected?
- wwbn/avideo (Packagist) <= 29.0, ECOSYSTEM:introduced=0,last_affected=29.0; WWBN AVideo <= 29.0, 29.0 and earlier.
- Is there a fix for CVE-2026-47694?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47694 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47694?
- Check whether you run wwbn/avideo (Packagist) or WWBN AVideo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stored cross-site scripting (XSS) vulnerability exists in WWBN AVideo versions up to 29.0. The root cause is the lack of output encoding or sanitization of the 'category_description' field in the Gallery plugin's 'mainAreaCategory.php' view. An attacker with category creation or editing privileges can inject a malicious JavaScript payload into the description field via 'objects/categoryAddNew.json.php'. When a victim (user or administrator) views the affected Gallery or category page, the payload executes in their browser context. This can be used to hijack sessions, steal sensitive information, or perform unauthorized administrative actions. A fix involving 'htmlspecialchars()' or 'HTMLPurifier' is recommended.
Affected products
- WWBN AVideo <= 29.0
Identifiers
- CVE-2026-47694
- GHSA-c8h8-vq34-9fw2
Timeline
- 2026-05-19: disclosed: Initial disclosure on GitHub
- 2026-05-29: advisory: NVD publication date
- 2026-06-04: advisory: GitHub Advisory published