AVideo vulnerable to unauthenticated SSRF via HTTP redirect bypass in LiveLinks proxy

Exploitation

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

CVSS

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

EPSS

• CVE-2026-33039: 0.46% estimated exploitation activity in the next 30 days; percentile 40.03 (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 The plugin/LiveLinks/proxy.php endpoint validates user-supplied URLs against internal/private networks using isSSRFSafeURL(), but only checks the initial URL. When the initial URL responds with an HTTP redirect (Location header), the redirect target is fetched via fakeBrowser() without re-validation, allowing an attacker to reach internal services (cloud metadata, RFC1918 addresses) through an attacker-controlled redirect. Affected Component - plugin/LiveLinks/proxy.php — lines 38-42 (redirect handling without SSRF re-validation) - objects/functionsBrowser.php — fakeBrowser() (line 123, raw cURL fetch with no SSRF protections) Description Missing SSRF re-validation after HTTP redirect The proxy.php endpoint validates the user-supplied livelink parameter against internal networks on line 18, using the comprehensive isSSRFSafeURL() function (which blocks private IPs, loopback, link-local/metadata, cloud metadata hostnames, and resolves DNS to detect rebinding). However, after…

Published by the source

17 Mar 2026, 20:33 UTC

Last modified by the source

20 Mar 2026, 21:22 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9x67-f2v7-63rw

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

# Patch Next advisory brief: CVE-2026-33039

Advisory: AVideo vulnerable to unauthenticated SSRF via HTTP redirect bypass in LiveLinks proxy
IDs: CVE-2026-33039, GHSA-9x67-f2v7-63rw
Record: https://patchnext.com/advisories/cve-2026-33039 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
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 <= 25.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-9x67-f2v7-63rw (GitHub-reviewed advisory GHSA-9x67-f2v7-63rw lists affected ranges: Packagist wwbn/avideo >=0 <=25.0)

Commands are suggestions: review each one before running it.