AVideo has SSRF Protection Bypass via HTTP Redirect in Image Download Endpoints

Exploitation

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

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-33766: 0.24% estimated exploitation activity in the next 30 days; percentile 15.43 (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 isSSRFSafeURL() validates URLs against private/reserved IP ranges before fetching, but urlgetcontents() follows HTTP redirects without re-validating the redirect target. An attacker can bypass SSRF protection by redirecting from a public URL to an internal target. Root Cause Check-time: isSSRFSafeURL() at objects/functions.php:4066 resolves the hostname and validates the IP. Use-time: urlgetcontents() at objects/functions.php:1990 calls filegetcontents() with PHP's default followlocation=1 — redirects are followed without re-validation. The wget fallback at line 2047 also follows redirects by default. Affected endpoint: objects/aVideoEncoderReceiveImage.json.php at lines 67-68, 107-108, 135-136, 160-161: Proof of Concept 1. Attacker sets up https://attacker.com/redir to respond with 302 Location: http://169.254.169.254/latest/meta-data/ 2. Authenticated user (with upload+edit permissions) triggers image download: 3. isSSRFSafeURL() resolves attacker.com → public IP → passes…

Published by the source

26 Mar 2026, 18:10 UTC

Last modified by the source

8 Apr 2026, 23:16 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f359-r3pv-2phf

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

# Patch Next advisory brief: CVE-2026-33766

Advisory: AVideo has SSRF Protection Bypass via HTTP Redirect in Image Download Endpoints
IDs: CVE-2026-33766, GHSA-f359-r3pv-2phf
Record: https://patchnext.com/advisories/cve-2026-33766 (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: Medium (CVSS 5.3)
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-f359-r3pv-2phf (GitHub-reviewed advisory GHSA-f359-r3pv-2phf lists affected ranges: Packagist wwbn/avideo >=0 <=26.0)

Commands are suggestions: review each one before running it.