Skip to main content
VulnerabilityPublished Updated

CVE-2023-47861: WWBN AVideo · Cross-site Scripting

Affects WWBN AVideoSource CVE Database V5

0

Not known to be exploited · CVSS 9.0 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WWBN AVideoAffected
  • =11.6
Fixed in–

AI-suggested

Immediate mitigation should focus on input validation and output encoding within the AVideo platform, specifically sanitizing the user name field in channelBody.php to neutralize any embedded scripts. Until an official patch is released, administrators should implement web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting this parameter. Restricting user privileges to the minimum necessary can reduce the impact of exploitation. User education campaigns should warn about phishing attempts that could deliver malicious links exploiting this vulnerability. Monitoring web server logs for suspicious HTTP requests targeting the user name parameter can help detect attempted exploitation. Additionally, organizations should consider isolating or segmenting the AVideo service to limit lateral movement if compromise occurs. Regular backups and incident response plans should be updated to address potential XSS incidents. Finally, organizations should track vendor communications for patches and apply them promptly once available.

Description

A cross-site scripting (xss) vulnerability exists in the channelBody.php user name functionality of WWBN AVideo 11.6 and dev master commit 15fed957fb. A specially crafted HTTP request can lead to arbitrary Javascript execution. An attacker can get a user to visit a webpage to trigger this vulnerability.

References

Community reviews

Loading reviews…