Advisory record · GHSA-9hv9-gvwm-95f2

AVideo Allows Unauthenticated Live Stream Control via Token Verification URL Override in control.json.php

CVSS 9.4 CriticalCriticalEPSS 0.0050 · 43rd percentile

Critical, because:

  • CVSS score 9.4: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 25 Mar 2026, 21:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wwbn/avideoPackagist<=26.0No fixed version yet
Identifiers
GHSA-9hv9-gvwm-95f2 · CVE-2026-33716 · PKSA-7gff-yt7v-8bkx
Weakness (CWE)
CWE-287
Published
25 Mar 2026
Updated
25 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GHSA-9hv9-gvwm-95f2 affects the Packagist package wwbn/avideo at versions 26.0 and below, and no fixed version is listed. The live stream control endpoint at plugin/Live/standAloneFiles/control.json.php accepts a user-supplied streamerURL parameter that redirects token verification to an attacker-chosen server, so an unauthenticated remote attacker can bypass authentication. They can then drop active live broadcasts, start recordings, and check whether stream names are active. No fix is listed; the advisory suggests removing the streamerURL parameter override.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.4 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0050, the 43rd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:25 UTC First seen by agentprime
  2. 31 Oct 2026, 14:25 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.