Skip to main content
VulnerabilityPublished Updated

CVE-2026-27568: WWBN AVideo · Cross-site Scripting

Affects WWBN AVideoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 21.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 21.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade AVideo and wwbn/AVideo to 21.0.

Affected software

ProductAffectedFixed in
WWBNAVideoAffected
  • <21.0
Fixed in
  • 21.0
GitHubwwbn/AVideopkg:github/wwbn/AVideoOther threatsAffected
  • <21.0
Fixed in
  • 21.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should upgrade WWBN AVideo to version 21.0 or later, where Parsedown Safe Mode is enabled and unsafe URI schemes are properly sanitized. Until upgrading is possible, administrators should implement input validation to explicitly block unsafe URI schemes such as 'javascript:', 'data:', and other potentially dangerous protocols in Markdown links within comments. Enabling Parsedown Safe Mode manually, if feasible, will reduce the risk of unsafe content rendering. Additionally, applying Content Security Policy (CSP) headers can help mitigate the impact of XSS by restricting the execution of inline scripts and untrusted sources. Monitoring user comments for suspicious links and educating users about the risks of clicking unknown links can further reduce exploitation chances. Regularly auditing and sanitizing user-generated content and limiting comment posting privileges to trusted users can also help contain risk.

Description

WWBN AVideo is an open source video platform. Prior to version 21.0, AVideo allows Markdown in video comments and uses Parsedown (v1.7.4) without Safe Mode enabled. Markdown links are not sufficiently sanitized, allowing `javascript:` URIs to be rendered as clickable links. An authenticated low-privilege attacker can post a malicious comment that injects persistent JavaScript. When another user clicks the link, the attacker can perform actions such as session hijacking, privilege escalation (including admin takeover), and data exfiltration. Version 21.0 contains a fix. As a workaround, validate and block unsafe URI schemes (e.g., `javascript:`) before rendering Markdown, and enable Parsedown Safe Mode.

References

Community reviews

Loading reviews…