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

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

- **Identifiers:** `GHSA-9hv9-gvwm-95f2` · `CVE-2026-33716` · `PKSA-7gff-yt7v-8bkx`
- **State:** Confirmed
- **Severity:** CVSS 9.4 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 25 Mar 2026
- **Updated:** 25 Mar 2026
- **Reviewed by a person:** No

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.

## Critical

Critical, because:

- CVSS score 9.4: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `wwbn/avideo` (Packagist): affected `<=26.0`; no fixed version yet

## 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

- 9.4 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`, from 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

- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9hv9-gvwm-95f2)

## Sources

- [GitHub Advisory Database: GHSA-9hv9-gvwm-95f2](https://github.com/advisories/GHSA-9hv9-gvwm-95f2)
- [OSV: GHSA-9hv9-gvwm-95f2](https://osv.dev/vulnerability/GHSA-9hv9-gvwm-95f2)
- <https://github.com/WWBN/AVideo/security/advisories/GHSA-9hv9-gvwm-95f2>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33716>
- <https://github.com/WWBN/AVideo/commit/388fcd57dbd16f6cb3ebcdf1d08cf2b929941128>
- <https://github.com/WWBN/AVideo>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-9hv9-gvwm-95f2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9hv9-gvwm-95f2/>. Everything for agents: <https://agentprime.io/llms.txt>.
