# CVE-2026-33039: AVideo vulnerable to unauthenticated SSRF via HTTP redirect bypass in LiveLinks proxy

> Unauthenticated attackers can bypass SSRF protections in AVideo's LiveLinks proxy via HTTP redirects to access internal network resources.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-9x67-f2v7-63rw

## What is CVE-2026-33039?

CVE-2026-33039 is a high-severity server-side request forgery vulnerability in Wwbn Avideo, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. In versions 25.0 and below, 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. This issue is fixed in version 26.0.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-33039?

2 open source packages ship an affected version, including wwbn/avideo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wwbn/avideo` | Packagist | All versions to 25.0 | None |
| `wwbn/avideo` | Packagist | All versions to 25.0 | None |

Products: Wwbn Avideo.

## How do I fix CVE-2026-33039?

No fix has been published for CVE-2026-33039 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33039 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33039 exists.

## Other vulnerabilities in Wwbn Avideo

- [CVE-2026-40911](https://insights.sbomify.com/CVE-2026-40911/): WWBN AVideo YPTSocket WebSocket Broadcast Relay Leads to Unauthenticated Cross-User JavaScript Execution via Client-Side eval() Sinks (critical 10.0)
- [CVE-2026-33478](https://insights.sbomify.com/CVE-2026-33478/): AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection (critical 10.0)
- [CVE-2022-30534](https://insights.sbomify.com/CVE-2022-30534/): Command injection in AVideo (critical 9.9)
- [CVE-2022-30547](https://insights.sbomify.com/CVE-2022-30547/): Path traversal in AVideo (critical 9.9)
- [CVE-2022-32572](https://insights.sbomify.com/CVE-2022-32572/): Command injection in AVideo (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33039 and fix it if it is affected.

What it is: CVE-2026-33039 is a high-severity server-side request forgery vulnerability in Wwbn Avideo, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33039 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 25.0; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 25.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33039/ (Markdown: https://insights.sbomify.com/CVE-2026-33039/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33039
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33039
- OSV: https://osv.dev/vulnerability/CVE-2026-33039

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33039/
Summaries are generated and may contain mistakes; the official description above is the record.