Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-82645 – Unauthenticated Stream Credential Disclosure – AVideo (commit e01e41ecc and earlier

Be the first to know when new zero-days emerge:

Summary

CVE-2026-82645 is a critical improper-verification-of-cryptographic-signature vulnerability (CWE-347) in AVideo’s Live plugin. An unauthenticated attacker can forge a token accepted by the getLiveKey.json.php endpoint to retrieve any user’s external streaming credentials (stream key and URL for platforms such as YouTube, Facebook, and Twitch). The flaw carries a CVSS v4.0 base score of 9.2 (Critical).

Technical details

  • Root cause: the getLiveKey.json.php endpoint in the Live plugin (plugin/Live/view/Live_restreams/getLiveKey.json.php) accepts a token request parameter that, when present, bypasses both the Live::canRestream() authorization gate and the restream ownership check.
  • The token is generated as encryptString() of a plain integer ID, with no binding to a user, no expiration, and no authentication tag (MAC).
  • Encryption uses AES-256-CBC with a deterministic (fixed) initialization vector, and the server-side parser uses intval(), which accepts any string beginning with a digit — enabling ciphertext manipulation.
  • The publicly reachable url2Embed.json.php endpoint functions as an encryption oracle, letting an attacker construct valid forged tokens without any credentials.
  • Attack vector: fully network-based, unauthenticated, no user interaction required.
  • Impact: disclosure of another user’s stream_key and stream_url, allowing an attacker to broadcast to that user’s connected YouTube, Facebook, or Twitch channel under their identity. Researchers demonstrated retrieval of victim credentials in roughly 76 seconds using 269 unauthenticated requests.

Affected software

  • WWBN AVideo, current commit e01e41ecc and all earlier versions (per vendor advisory; no version boundary or patched release has been published at this time).

Severity

  • CVSS v4.0: 9.2 (Critical) — 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
  • CVSS v3.1: 8.6 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: No patched version has been released yet. Monitor the vendor’s GitHub security advisory (GHSA-c4w3-h888-7ccv) for a fix and apply it as soon as it becomes available.
  • Workarounds: Restrict or disable public access to the Live plugin’s restream endpoints (getLiveKey.json.php, url2Embed.json.php) at the web server or reverse proxy layer until a patch ships; rotate all existing restream stream keys/URLs for connected platforms (YouTube, Facebook, Twitch); monitor authentication and Live plugin logs for repeated/rapid requests to these endpoints, which may indicate token-forging attempts.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Sign In - AVideo, AVideo
  • Raw response body: id="avideoModal", avideoAlert(, avideoModalIframe(

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge