AVideo has Unauthenticated SSRF via webSiteRootURL Parameter in saveDVR.json.php, Chaining to Verification Bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-33351: 0.44% estimated exploitation activity in the next 30 days; percentile 38.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A Server-Side Request Forgery (SSRF) vulnerability exists in plugin/Live/standAloneFiles/saveDVR.json.php. When the AVideo Live plugin is deployed in standalone mode (the intended configuration for this file), the $REQUEST['webSiteRootURL'] parameter is used directly to construct a URL that is fetched server-side via filegetcontents(). No authentication, origin validation, or URL allowlisting is performed. Affected Component File: plugin/Live/standAloneFiles/saveDVR.json.php, lines 5-28 Root Cause 1. User-controlled URL base: When the configuration file does not exist (standalone deployment), $streamerURL is set directly from $REQUEST['webSiteRootURL'] with no validation. 2. No URL allowlisting or scheme restriction: The value is used as-is in a filegetcontents() call. There is no check for http/https scheme only, no private IP blocking, and no domain allowlist. 3. Verification bypass by design: The token verification URL is constructed using the attacker-controlled base URL.…

Published by the source

19 Mar 2026, 19:13 UTC

Last modified by the source

25 Mar 2026, 18:49 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5f7v-4f6g-74rj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33351

Advisory: AVideo has Unauthenticated SSRF via `webSiteRootURL` Parameter in saveDVR.json.php, Chaining to Verification Bypass
IDs: CVE-2026-33351, GHSA-5f7v-4f6g-74rj
Record: https://patchnext.com/advisories/cve-2026-33351 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist wwbn/avideo: affected <= 26.0

## Suggested inspection (read-only)
- Packagist wwbn/avideo: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wwbn/avideo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5f7v-4f6g-74rj (GitHub-reviewed advisory GHSA-5f7v-4f6g-74rj lists affected ranges: Packagist wwbn/avideo >=0 <=26.0)

Commands are suggestions: review each one before running it.