Quick answers
- Is CVE-2026-105086 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105086 being exploited in the wild.
- How severe is CVE-2026-105086?
- High severity, with a CVSS score of 8.7, published 4 October 2026.
- Which products and versions are affected?
- WWBN AVideo 12.4 through 29.2.0.
- Is there a fix for CVE-2026-105086?
- A patch was published on 2026-10-04: Security fix committed on 2026-10-04 to sanitize video titles and descriptions Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105086 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-105086?
- Check whether you run 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
The safeString() function strips HTML tags before decoding HTML entities, but the function is called twice during video save (in setTitle() and save()), allowing double-encoded entities like "&<" to bypass the first pass and become executable tags after the second pass. An authenticated attacker can inject HTML/JavaScript via the video title parameter in videoAddNew.json.php; the payload is stored unescaped and echoed without escaping in trending.php, videoEmbeded.php, YouPHPFlix2 gallery rows, and playlist.php, executing in visitors' browsers without Content-Security-Policy protection.
Affected products
- WWBN AVideo 12.4 through 29.2.0
Timeline
- 2026-10-04: disclosed
- 2026-10-04: patched: Security fix committed on 2026-10-04 to sanitize video titles and descriptions