External risk intelligence

WWBN AVideo Node Socket Server Cross-Site Scripting Account Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130650

AVideo is a video platform and content management system typically deployed as a public-facing web application. Since the vulnerable component relates to the application's node socket server which is exposed to handle web traffic, it is commonly accessible from the internet.

Cross-site Scripting

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in the WWBN AVideo platform, specifically within its node socket server, allowing unauthenticated attackers to potentially take over administrator accounts. The issue arises from improper handling of code execution within HTML, enabling attackers to trigger code in administrators' browsers. The main concern is confirming relevance and exposure given the potential for account takeover.

  • Attackers can execute code on administrator browsers.
  • This vulnerability could lead to unauthorized account access.
  • Confirm if your video platform is affected.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can initiate a connection to the WWBN AVideo application, obtain an anonymous token, and send a specially crafted message. This message can trigger the execution of arbitrary code within the browsers of unsuspecting administrators. The vulnerability stems from the default node socket server's failure to properly filter HTML content before evaluating code.

  • No authentication required.
  • Spoofed message triggers code execution.
  • Risk of administrator account takeover.

Live Threat

Current exploitation, exposure, and threat context

The WWBN AVideo platform's default node socket server could allow unauthenticated attackers to execute arbitrary code in administrators' browsers. This could occur when an attacker sends a specially crafted message, potentially leading to an account takeover if the server relays code evaluation without proper sanitization.

  • Administrator browser sessions at risk.
  • Attacker sends a spoofed message.
  • Could lead to account takeover.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in WWBN AVideo's node socket server can allow unauthenticated attackers to achieve account takeover through client-side code execution. Technical leaders and security teams should prioritize identifying all instances of AVideo, confirming their exposure and business criticality, and then engaging the accountable application or platform owner to plan remediation.

  • Accountable teams must own the issue.
  • Verify AVideo's external reachability.
  • Plan remediation based on business risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is WWBN AVideo?

WWBN AVideo is an open-source platform designed for hosting, managing, and streaming video content. It functions as a content management system that includes a node socket server to handle real-time communication between the server and users' web browsers, which is essential for interactive video platform features.

What is the nature of the CVE-2026-130650 vulnerability?

This is a cross-site scripting (CWE-79) vulnerability. It occurs because the node socket server improperly relays certain code evaluation instructions without filtering. This allows malicious data to be processed as executable code within a victim's browser rather than being treated as harmless text.

How does an attacker trigger this vulnerability?

An attacker initiates the process by connecting to the AVideo node socket server to obtain an anonymous token. Once connected, they send a spoofed message that instructs the server to relay malicious code. The vulnerability does not require authentication, but it relies specifically on the server's failure to sanitize inputs before they reach the administrator's browser.

Is my AVideo instance at risk according to Halo Surface Signal?

Halo Surface Signal indicates that AVideo is typically deployed as a public-facing web application. Because the affected node socket server is designed to handle web traffic, your instance is likely reachable from the internet, increasing the relevance of this vulnerability if your platform is exposed.

What steps should I take if I run AVideo?

First, verify all instances of AVideo within your environment and confirm their current network exposure. Since this is a critical issue involving potential account takeover, engage your application platform owners immediately to assess the business risk and begin planning for the necessary security updates.

References