Description
AVideo (current commit e01e41ecc and earlier) exposes stream credentials through the plugin/Live/view/Live_restreams/getLiveKey.json.php endpoint. Supplying a 'token' request parameter waives both the Live::canRestream() access gate and the restream ownership check, causing the endpoint to return any restream's stream_key and stream_url (credentials for external platforms such as YouTube, Facebook, and Twitch) without authentication. The token is merely encryptString() of an integer id with no user binding, expiry, or authentication tag. Because encryption uses AES-256-CBC with a deterministic IV and no MAC, and because intval() accepts any string beginning with a digit, an unauthenticated attacker can forge valid tokens using the public encryption oracle in view/url2Embed.json.php, disclosing arbitrary users' stream credentials.
Published: 2026-08-30
Score: 9.2 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability lies in the AVideo Live_restreams plugin, which accepts a token parameter that disables both the restream permission check and the ownership validation. The token is simply an AES-256-CBC encrypted integer ID without an authentication tag or user association. Because the IV is deterministic and no MAC is applied, anyone can forge tokens, resulting in the endpoint revealing any user's stream_key and stream_url for external platforms such as YouTube, Facebook, or Twitch. The flaw allows an attacker to obtain sensitive credentials that enable unauthorized broadcast to third‑party services, thereby exposing confidentiality and potentially allowing further malicious activity such as impersonation or data exfiltration through the stream channel.

Affected Systems

This flaw affects the WWBN AVideo product, specifically versions released before commit e01e41ecc. The vulnerability is present in all releases up to and including that commit, regardless of the operating system or deployment environment.

Risk and Exploitability

The CVSS score of 9.2 indicates critical severity, and the lack of authentication or rate limiting on the endpoint makes exploitation trivial for an unauthenticated attacker. Although EPSS data is not available, the deterministic nature of the encryption and public oracle in the view/url2Embed.json.php endpoint make token forging straightforward. The issue is not listed in the CISA KEV catalog, but the high CVSS and obvious attack path warrant immediate attention.

Generated by OpenCVE AI on August 30, 2026 at 15:26 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade AVideo to the latest release that removes the insecure token logic or applies a patch that requires token validation with an authenticated encryption scheme.
  • Disable or secure the Live_restreams/getLiveKey.json.php endpoint, ensuring it requires prior authentication and proper ownership checks.
  • Replace the current AES-256-CBC token mechanism with an authenticated encryption method (e.g., AES-GCM) that includes a MAC and a random IV, and bind the token to the requesting user.
  • After the vendor patch is applied, configure the server to enforce HTTPS and enable IP filtering or rate limiting on sensitive endpoints to mitigate brute‑force or replay attempts.

Generated by OpenCVE AI on August 30, 2026 at 15:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 30 Aug 2026 14:45:00 +0000

Type Values Removed Values Added
Description AVideo (current commit e01e41ecc and earlier) exposes stream credentials through the plugin/Live/view/Live_restreams/getLiveKey.json.php endpoint. Supplying a 'token' request parameter waives both the Live::canRestream() access gate and the restream ownership check, causing the endpoint to return any restream's stream_key and stream_url (credentials for external platforms such as YouTube, Facebook, and Twitch) without authentication. The token is merely encryptString() of an integer id with no user binding, expiry, or authentication tag. Because encryption uses AES-256-CBC with a deterministic IV and no MAC, and because intval() accepts any string beginning with a digit, an unauthenticated attacker can forge valid tokens using the public encryption oracle in view/url2Embed.json.php, disclosing arbitrary users' stream credentials.
Title AVideo Unauthenticated Stream Credential Disclosure via Forgeable Token
First Time appeared Wwbn
Wwbn avideo
Weaknesses CWE-347
CPEs cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*
Vendors & Products Wwbn
Wwbn avideo
References
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N'}

cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-30T14:33:28.997Z

Reserved: 2026-08-30T13:38:00.101Z

Link: CVE-2026-82645

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-30T15:16:44.863

Modified: 2026-08-30T15:16:44.863

Link: CVE-2026-82645

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-30T16:00:13Z

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature