/

CVE-2026-89250

Severity:

HIGH RISK

(7.5)

Missing Authentication (CWE-306) in WWBN AVideo Endpoint

CVE-2026-89250

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized disclosure of recorded video files

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

WWBN AVideo contains an unauthenticated file-read vulnerability in the getRecordedFile.php endpoint, which streams recorded FLV files from a temporary directory. An attacker who knows or guesses a stream key may be able to download recorded live video without authentication or authorization.

Affected context

The vulnerability occurs in deployments where the getRecordedFile.php endpoint is reachable and recorded FLV files are available through the temporary-directory streaming path. Risk is higher when stream keys are predictable, exposed, reused, or accepted without an additional authenticated session or authorization check.

Exploit preconditions

  • Attack surface: The HTTP endpoint that serves recorded FLV files
  • Required access: Network access to the endpoint; no authenticated account may be required
  • Trigger point: A request that references a valid, known, or guessed stream key
  • Why exploitation is possible: The endpoint may stream the associated file without verifying the caller's identity or authorization

Why this happens

The underlying bug is a missing authentication and authorization control on a file-serving endpoint. The application uses a stream key to locate recorded content but does not establish that the requester is an authenticated and authorized user before returning the file. This behavior maps to CWE-306, which covers missing authentication for a critical function.

Potential impact

  • Attackers may download recorded live video files
  • Private or sensitive video content could be disclosed
  • Organizations may face privacy, compliance, or reputational consequences
  • Repeated requests could increase storage or bandwidth consumption

General mitigation guidance

Mitigation generally focuses on enforcing identity and authorization at every

protected file-serving boundary.

Common defensive patterns include:

  • Require authenticated sessions or equivalent access tokens before serving recordings
  • Authorize access based on the specific recording, stream, tenant, or owner
  • Treat stream keys as identifiers rather than authentication credentials
  • Use high-entropy, short-lived access tokens where delegated access is needed
  • Keep recorded files outside directly reachable temporary or web-served paths
  • Apply least-privilege permissions to the process and storage locations
  • Return consistent access-denied responses without revealing file existence

How teams detect issues like this

Organizations can detect similar issues through:

  • Static analysis checks for file-serving routes lacking authentication middleware
  • Code review of endpoints that map request parameters or keys to filesystem objects
  • Tests that verify unauthenticated and cross-user requests cannot retrieve recordings
  • Web-server and application logging for repeated requests using invalid or varying stream keys
  • Policy enforcement requiring authentication and object-level authorization for media endpoints
  • Automated security review tools that identify exposed sensitive-file access paths

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-crcx-7mx7-jqfr
vulncheck.comvulncheck.com/advisories/wwbn-avideo-unauthenticated-file-read-via-getrecordedfile-php

Frequently asked

questions

It may be remotely exploitable when the file-serving endpoint is network-accessible

and an attacker can supply a valid, known, or guessed stream key.

The described flaw does not require an authenticated account if the endpoint

is reachable and accepts the stream key without performing authentication or

authorization checks.

Require authentication and object-level authorization before locating or

streaming any recorded file. Stream keys should not be treated as the sole

security control.

Apply consistent access-control middleware to media endpoints, test anonymous

and cross-tenant access paths, keep recordings outside direct public paths, and

monitor suspicious file-access patterns.

Find out what's already
exploitable in your codebase.