External risk intelligence

WWBN AVideo Stored Cross-Site Scripting Vulnerability in User Group Management.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-89243

The vulnerability requires high-privileged administrator access to manipulate user group settings and relies on another administrator interacting with the interface. While the application may be internet-facing, this specific attack surface is restricted to administrative functions rather than public-facing endpoints.

Cross-site Scripting

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a security vulnerability in WWBN AVideo software that could allow an administrator to inject malicious code, impacting other administrators who manage user groups. The primary concern is confirming if this specific type of administrative access and user interaction exists within your environment.

  • Malicious code can be hidden in user group names.
  • Affects administrators managing other administrators.
  • Confirm relevance and potential exposure within your system.

Attack Path

How an attacker could exploit the issue

An attacker with administrative privileges can exploit this vulnerability by manipulating user group names to inject malicious code. This code will execute when another administrator accesses the user management interface, potentially leading to further compromise.

  • Requires administrator access to modify group names.
  • Triggered when another administrator views user groups.
  • Risk of code execution in administrative browsers.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, administrators with `canAdminUserGroups` permission could inject malicious code into group names. This code may execute in the browser when other administrators access the user manager interface.

  • Administrator-level user group data.
  • Injecting malicious code into group names.
  • Arbitrary code execution in administrator browsers.

Operational Fix

Recommended remediation, mitigation, and detection steps

The application owner is responsible for addressing this vulnerability, as it affects a specific feature within the AVideo application. The first practical step is to confirm the existence and reachability of AVideo instances within your environment, identify the accountable administrator, and then coordinate remediation efforts, possibly during a scheduled maintenance window.

  • Application owner to address.
  • Verify AVideo instance reachability.
  • Plan remediation by 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 used for hosting, streaming, and managing video content, similar to a self-hosted YouTube or specialized media server. It includes features for user management and permission handling, which allow administrators to organize contributors and viewers into specific groups.

What does CVE-2026-89243 mean for security?

This vulnerability is a Stored Cross-Site Scripting (XSS) issue. It means the software does not properly clean text input when naming user groups. Because this input is saved, an attacker can store malicious JavaScript in a group name; that script then runs automatically in the web browser of any other administrator who views that group.

How is this vulnerability triggered?

The bug requires two steps: first, an authenticated user with administrative permissions must deliberately inject malicious code into a user group name. It is not triggered by public users or by simply visiting the site. The malicious code only executes when a different administrator later opens the specific user management dashboard where that group name is displayed.

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

Halo Surface Signal labels the risk as 'Unlikely' because the attack surface is restricted to internal administrative functions. While the application itself may be internet-facing, this specific vulnerability cannot be triggered through public endpoints; it requires an existing, high-privileged administrative account to be compromised or acting maliciously.

What should I do if I run AVideo?

Your first step is to locate all instances of AVideo running in your environment to understand your footprint. Once identified, confirm which team members hold administrative access to user group settings. Since this is an application-level flaw, coordinate with your technical team to plan a maintenance update or remediation based on your internal risk management policies.

References