/

CVE-2026-89243

Severity:

HIGH RISK

(8.1)

Stored XSS (CWE-79) in WWBN AVideo User Groups Panel

CVE-2026-89243

Deferred

Vulnerability type

Category:

Stored Cross-Site Scripting

CWE:

CWE-79

Impact:

Administrative session compromise and unauthorized browser-side actions

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A stored cross-site scripting vulnerability in WWBN AVideo allows an administrator with user-group management permission to save unsanitized HTML or JavaScript in a group name. The payload may execute in the browsers of other administrators when they open the user manager interface.

Affected context

The vulnerability occurs in the user-group management workflow when the

group_name value is accepted by UserGroups::setGroup_name() without

adequate output encoding or input sanitization. It is relevant to deployments

where an administrator with canAdminUserGroups permission can create or

modify groups and other administrators later view those names in the user

manager interface.

Exploit preconditions

  • Attack surface: The administrative user-group management interface
  • Required access: An authenticated account with canAdminUserGroups permission
  • Trigger point: Affected administrators viewing the stored group name in the user manager
  • Why exploitation is possible: User-controlled group-name content is stored and later rendered in an administrative browser context without sufficient neutralization

Why this happens

The underlying bug is a failure to treat administrative form input as

untrusted data throughout its storage and rendering lifecycle. The group name

is persisted without an appropriate encoding or sanitization boundary, and

later output is interpreted as browser markup or script rather than displayed

strictly as text. This behavior maps to CWE-79: Improper Neutralization of Input During Web Page Generation, commonly known as cross-site scripting.

Potential impact

  • Malicious script may execute in another administrator's browser
  • An attacker could perform unauthorized actions using the victim's active session
  • Sensitive administrative data could be exposed through the affected interface
  • Administrative workflows could be altered or abused
  • The application could experience broader compromise if privileged browser capabilities are available

General mitigation guidance

Mitigation generally focuses on ensuring that user-controlled values remain

inert wherever they are displayed.

Common defensive patterns include:

  • Apply context-appropriate output encoding at every rendering sink
  • Treat group names and similar metadata as untrusted input even when submitted by administrators
  • Use allowlisted validation for expected name characters and length
  • Avoid rendering stored values as raw HTML unless a narrowly controlled and reviewed use case requires it
  • Apply defense-in-depth browser policies such as a restrictive Content Security Policy
  • Limit user-group administration permissions according to least privilege
  • Preserve safe handling consistently across create, update, display, and API paths

How teams detect issues like this

Detection can combine static analysis, code review, and runtime controls:

  • Search for database-backed values rendered into HTML without context-aware encoding
  • Review setters, templates, and UI components handling group_name and related metadata
  • Flag raw HTML insertion APIs, string concatenation into markup, and disabled escaping
  • Add automated tests that verify stored special characters are rendered as text
  • Use dynamic application security testing to identify persistent input that executes when viewed by another role
  • Enforce secure output-encoding and content-security policies through CI and application security checks

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-qm3h-2jrx-xmg6
vulncheck.comvulncheck.com/advisories/wwbn-avideo-stored-xss-via-usergroups-setgroup-name

Frequently asked

questions

An attacker generally needs an authenticated account with permission to manage

user groups. The required permission reduces the attack surface but does not

eliminate the risk to other administrators.

The payload may execute when another administrator opens the user manager

interface and the affected group name is rendered.

Treat group names as plain text and apply context-aware output encoding at the

point where values are inserted into HTML. Validation and sanitization can

provide additional defense but should not replace correct output encoding.

Use framework auto-escaping, test stored input across privileged interfaces,

review raw markup operations, and apply least privilege to administrative

permissions.

Find out what's already
exploitable in your codebase.