SEPTEMBER 14, 2026
Live Feed
Back to database
Case File

CVE-2026-88875

MEDIUM · CVSS 4.3 EPSS 0.22% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-10 · Last synced 2026-09-14

CyberRota Analysis

AI-Generated

AVideo's API is vulnerable due to inadequate sanitization of sensitive user fields in the video response, allowing low-privilege authenticated users to access another user's email address, account name, and permissions. This could lead to unauthorized information disclosure, posing a risk to user privacy and account security. Organizations utilizing AVideo should prioritize addressing this vulnerability, especially those with user-generated content or sensitive user data.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

GitHub PoC Links

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-88875
Severity
MEDIUM
CVSS
4.3
EPSS
0.22%

Original NVD Description

AVideo through revision c3edcc274c389816d434acadac07ee78eaf330c1 (master, 2026-08-23) incompletely sanitizes sensitive user fields in the APIName=video response. Video rows include columns joined from the video owner's user record, and API::get_api_video() calls removeSensitiveUserFields() only when the caller is neither authenticated nor using a valid API secret; it never compares User::getId() with the row's users_id. As a result, any low-privilege authenticated account can request another user's video and receive the owner's email address, account name (user), and isAdmin, canUpload and canStream flags, which are removed for guests and should be returned only to the owner or to callers with a valid API secret. No patched version was available at the time of the advisory.