CVE-2026-88867

8.7

WWBN · AVideo

WWBN AVideo contains a stored cross-site scripting (XSS) vulnerability allowing authenticated users to inject malicious scripts that execute in the browsers of other users, including administrators.

Executive summary

A stored cross-site scripting vulnerability in WWBN AVideo allows authenticated users with upload permissions to execute malicious JavaScript in the context of other users, posing a severe risk of account takeover.

Vulnerability

The application fails to sanitize the name and iconClass parameters in objects/categoryAddNew.json.php, allowing an authenticated user with canUpload permissions to store malicious XSS payloads that execute when viewed by other users, including administrators.

Business impact

Successful exploitation of this vulnerability allows an attacker to execute arbitrary JavaScript in the context of a victim's session. Given the CVSS score of 8.7, this is a high-severity issue that could lead to unauthorized actions performed on behalf of administrators, potentially resulting in full system compromise, data theft, or further malicious configuration changes.

Remediation

Immediate Action: Since no official patch is currently available, administrators should immediately disable the usersCanCreateNewCategories option in the AVideo configuration to prevent the exploitation of this vector.

Proactive Monitoring: Review web application logs for suspicious POST requests to objects/categoryAddNew.json.php and monitor administrative dashboards for anomalous script execution or unauthorized changes to category settings.

Compensating Controls: Deploy a Web Application Firewall (WAF) with strict XSS filtering rules to detect and block malicious payloads submitted via the category creation interface.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

The severity of this vulnerability necessitates immediate administrative intervention. Because a patch is not yet available, organizations must prioritize disabling the vulnerable functionality to eliminate the attack surface. Security teams should maintain heightened vigilance until a verified vendor update is released and applied to all affected instances.

More WWBN CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by santhreal, per the CVE Program record.