/

CVE-2026-88876

Severity:

HIGH RISK

(7.5)

Broken Access Control (CWE-200) in AVideo PlayerSkins

CVE-2026-88876

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-200

Impact:

Unauthorized Information Disclosure

Severity:

HIGH RISK

(7.5)

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

AVideo's PlayerSkins SEO endpoint may expose direct sources for password-protected videos without verifying the configured video password. An unauthenticated attacker who knows or can obtain a video identifier could request the endpoint and read protected media bytes.

Affected context

The issue occurs in the PlayerSkins plugin's seo.php endpoint when it processes a video identifier and calls getSources() without first enforcing the password requirement associated with the video. Deployments that expose this endpoint and rely on video-level passwords for access control may be affected, particularly when direct media URLs are retrievable from the response.

Exploit preconditions

  • Attack surface: The PlayerSkins seo.php HTTP endpoint
  • Required access: No authenticated account is required; the attacker needs a valid or discoverable video identifier
  • Trigger point: A request that causes getSources() to return the protected video's direct media source
  • Why exploitation is possible: Authorization is not checked before source metadata and the direct MP4 location are disclosed

Why this happens

The underlying bug is a missing authorization check in a code path that returns protected media sources. The endpoint treats possession of a video identifier as sufficient to retrieve source information, rather than consistently enforcing the video's configured password before disclosure. This behavior maps to CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, with an access-control failure enabling the exposure.

Potential impact

  • Attackers may obtain direct URLs for password-protected videos
  • Unauthorized users could read protected media content
  • Private or restricted video distribution controls may be bypassed
  • Exposed URLs could be copied, shared, or used for unauthorized bulk retrieval

General mitigation guidance

Mitigation generally centers on making authorization a mandatory part of every media-source retrieval path.

Common defensive patterns include:

  • Validate the configured video password or equivalent authorization state before calling source-generation functions
  • Apply authorization checks server-side rather than relying on obscurity of video identifiers or client-side controls
  • Avoid returning direct media URLs unless the requester has been authorized for that specific asset
  • Use short-lived, scoped media URLs or a controlled streaming proxy where appropriate
  • Enforce least privilege for media storage and delivery services
  • Centralize access-control decisions so alternate endpoints and plugins cannot bypass them

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review rules requiring authorization checks before sensitive source-generation or download functions
  • Review of routes that accept object identifiers and return direct file URLs or media bytes
  • Tests verifying that unauthenticated and incorrectly authenticated requests cannot access password-protected assets
  • Web logs showing repeated requests to media-source endpoints, enumeration of video identifiers, or downloads without corresponding authorization events
  • Policy enforcement requiring server-side authorization for every protected-object access path

Automated security review tools may help identify endpoints that disclose sensitive resources without nearby access-control checks.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-wq9m-cfw6-4gh5
vulncheck.comvulncheck.com/advisories/avideo-playerskins-seo-php-missing-authorization-password-protected-vod

Frequently asked

questions

Yes. It can be exercised through the exposed HTTP endpoint when the attacker can identify a target video and the deployment makes the endpoint reachable.

The described issue permits unauthenticated access. The key condition is the ability to supply a valid or discoverable video identifier, not possession of a user session.

Require server-side authorization, including the configured video-password validation, before generating or returning any protected media source.

Test every media and download route against unauthorized access, centralize authorization checks, avoid treating identifiers as credentials, and monitor for enumeration or unexplained source retrieval.

Find out what's already
exploitable in your codebase.