CVE-2026-88875: Exposure of Private Personal Information to an Unauthorized Actor in WWBN AVideo
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.
AI Analysis
Technical Summary
CVE-2026-88875 describes an information exposure vulnerability in WWBN AVideo through revision c3edcc274c389816d434acadac07ee78eaf330c1. The API method get_api_video() returns video data joined with the video owner's user record. The function removeSensitiveUserFields() is only called when the caller is unauthenticated or lacks a valid API secret, but it does not verify if the authenticated user is the owner of the video. Consequently, any authenticated user with low privileges can retrieve another user's email, username, and permission flags (isAdmin, canUpload, canStream) that should be restricted. This flaw leads to unauthorized disclosure of private personal information. No official fix or patch was available at the time of publication.
Potential Impact
The vulnerability allows unauthorized disclosure of private personal information including email addresses, usernames, and user permission flags to any authenticated user. This exposure can lead to privacy violations and potential misuse of user data. The CVSS 4.0 base score is 5.3 (medium severity), reflecting network attack vector, low attack complexity, no user interaction, and low impact on confidentiality. There is no indication of integrity or availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict API access to trusted users and monitor for unauthorized data access. Avoid using low-privilege accounts for sensitive API calls. Follow vendor updates for an official fix.
CVE-2026-88875: Exposure of Private Personal Information to an Unauthorized Actor in WWBN AVideo
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.
CVSS v4.0
Score 5.3medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-88875 describes an information exposure vulnerability in WWBN AVideo through revision c3edcc274c389816d434acadac07ee78eaf330c1. The API method get_api_video() returns video data joined with the video owner's user record. The function removeSensitiveUserFields() is only called when the caller is unauthenticated or lacks a valid API secret, but it does not verify if the authenticated user is the owner of the video. Consequently, any authenticated user with low privileges can retrieve another user's email, username, and permission flags (isAdmin, canUpload, canStream) that should be restricted. This flaw leads to unauthorized disclosure of private personal information. No official fix or patch was available at the time of publication.
Potential Impact
The vulnerability allows unauthorized disclosure of private personal information including email addresses, usernames, and user permission flags to any authenticated user. This exposure can lead to privacy violations and potential misuse of user data. The CVSS 4.0 base score is 5.3 (medium severity), reflecting network attack vector, low attack complexity, no user interaction, and low impact on confidentiality. There is no indication of integrity or availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict API access to trusted users and monitor for unauthorized data access. Avoid using low-privilege accounts for sensitive API calls. Follow vendor updates for an official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-10T11:24:26.196Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa2af40acd9273b492596df
Added to database: 09/10/2026, 13:23:12 UTC
Last enriched: 09/10/2026, 14:11:13 UTC
Last updated: 09/10/2026, 17:00:16 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.