Skip to main content
CVE-2026-88875VulnerabilityPublished 09/10/2026Updated 09/18/2026

CVE-2026-88875: WWBN AVideo · Exposure of Private Personal Information to an Unauthorized Actor

Affects WWBN AVideoSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 10/25/2026, 16:58:58 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
WWBNAVideoAffected
  • =0
Fixed in–

AI-suggested

Users should monitor the vendor's communications for updates. Until a fix is released, restricting API access to trusted users and minimizing the number of low-privilege authenticated accounts may reduce exposure risk.

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.

Impact

This vulnerability allows low-privilege authenticated users to access private personal information of other users, including email addresses and account privilege flags. This exposure can lead to privacy violations and potential misuse of user data. The CVSS 4.0 score is 5.3 (medium severity), reflecting the network attack vector, low attack complexity, no user interaction required, and limited confidentiality impact.

Summary

In WWBN AVideo (revision c3edcc274c389816d434acadac07ee78eaf330c1), the API method get_api_video() returns video data joined with the video owner's user record. The function removeSensitiveUserFields() is called only when the caller is unauthenticated or lacks a valid API secret, but it does not verify if the caller's user ID matches the video owner's user ID. Consequently, low-privilege authenticated users can retrieve sensitive fields such as the owner's email, username, and privilege flags (isAdmin, canUpload, canStream) for videos they do not own. These fields are intended to be hidden from guests and unauthorized users. No official fix or patch was available at the time of publication.

References

Community reviews

Loading reviews…