/

CVE-2026-86728

Severity:

HIGH RISK

(7.5)

Missing Authentication (CWE-306) in AVideo PlayLists

CVE-2026-86728

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized access to sensitive information and streaming credentials

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 PlayLists EPG endpoint may expose live-stream keys, server identifiers, private schedules, and related programme data without verifying the requester's identity. The issue becomes risky when the endpoint is internet-accessible and accepts predictable user or playlist identifiers.

Affected context

The vulnerability occurs in deployments using the AVideo PlayLists plugin where the EPG endpoint can be reached without an effective authentication check. Risk depends on whether the endpoint is exposed to untrusted clients, whether identifiers are predictable, and whether returned schedules or stream keys are considered private.

Exploit preconditions

  • Attack surface: The plugin/PlayLists/epg.json.php HTTP endpoint
  • Required access: Network access to the endpoint; no valid account may be required
  • Trigger point: A request referencing a user or playlist identifier
  • Why exploitation is possible: The endpoint may return protected EPG and credential-related data without first establishing the caller's identity and authorization

Why this happens

The underlying bug is an authorization boundary failure: a resource-serving endpoint processes identifier-based requests without requiring authentication or verifying access to the referenced data. This maps to CWE-306, Missing Authentication for Critical Function, because a function that exposes sensitive information can be reached before the application establishes an authenticated user context. Predictable identifiers can further increase the scope of unauthorized enumeration.

Potential impact

  • Attackers may obtain live-stream keys or other access credentials.
  • Attackers could disclose private EPG schedules and programme metadata.
  • Exposed server identifiers may assist reconnaissance and targeted attacks.
  • Compromised stream credentials could enable unauthorized viewing, reuse, or service disruption.

General mitigation guidance

Mitigation generally centers on enforcing authentication and object-level authorization before any EPG or playlist data is returned. Endpoints that expose private schedules or stream keys should use secure-by-default access controls, minimize returned fields, and avoid treating client-supplied identifiers as proof of ownership. Sensitive credentials can be separated from ordinary schedule data, rotated when exposure is suspected, and protected with least-privilege scopes. Additional controls may include consistent authorization middleware, rate limiting, non-enumerable resource references, and restrictive responses for unauthenticated requests.

How teams detect issues like this

Detection approaches may include static analysis and code review for sensitive endpoints that lack authentication middleware or authorization checks before database retrieval and response generation. Test suites can verify that anonymous requests, cross-account identifiers, and unauthenticated enumeration attempts receive denied responses and no sensitive fields. API inventories, gateway policies, access-log monitoring, and alerts for repeated sequential identifier requests can provide additional coverage. Automated application-security review tools may help identify missing authentication and object-level authorization patterns.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-xpr5-7246-qvh5
vulncheck.comvulncheck.com/advisories/avideo-through-29.0-unauthenticated-disclosure-via-epg-json-php

Frequently asked

questions

It may be remotely exploitable when the affected EPG endpoint is reachable over the network and does not require authentication.

The primary requirement is network access to the endpoint. A valid account may not be necessary, although deployment-level access controls can limit exposure.

Require authentication and verify authorization for the specific user or playlist before retrieving or returning EPG data, stream keys, or server identifiers.

Apply centralized authentication and object-level authorization, test anonymous and cross-tenant requests, minimize sensitive responses, and monitor for identifier enumeration.

Find out what's already
exploitable in your codebase.