# CVE-2026-33024: AVideo-Encoder has Unauthenticated Blind Server-Side Request Forgery via Public Thumbnail Generator

> Unauthenticated attackers can exploit blind SSRF in AVideo thumbnail endpoints to access internal network resources and cloud metadata.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA: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-h9gh-866r-6vgq

## What is CVE-2026-33024?

CVE-2026-33024 is a critical server-side request forgery vulnerability in WWBN AVideo-Encoder, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AVideo is a video-sharing Platform. Versions prior to 8.0 contain a Server-Side Request Forgery vulnerability (CWE-918) in the public thumbnail endpoints getImage.php and getImageMP4.php. Both endpoints accept a base64Url GET parameter, base64-decode it, and pass the resulting URL to ffmpeg as an input source without any authentication requirement. The prior validation only checked that the URL was syntactically valid (FILTER_VALIDATE_URL) and started with http(s)://. This is insufficient: an attacker can supply URLs such as http://169.254.169.254/latest/meta-data/ (AWS/cloud instance metadata), http://192.168.x.x/, or http://127.0.0.1/ to make the server reach internal network resources. The response is not directly returned (blind), but timing differences and error logs can be used to infer results. The issue has been fixed in version 8.0.

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

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

It affects 1 product.


Products: Wwbn Avideo-Encoder.

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

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

## Is CVE-2026-33024 being exploited?

There is no known exploitation of CVE-2026-33024 in the wild and no public exploit code.

## Other vulnerabilities in WWBN AVideo-Encoder

- [CVE-2026-29058](https://insights.sbomify.com/CVE-2026-29058/): AVideo: Unauthenticated OS Command Injection via base64Url in objects/getImage.php (critical 9.8)
- [CVE-2026-33025](https://insights.sbomify.com/CVE-2026-33025/): AVideo-Encoder is Vulnerable to Authenticated SQL Injection via ORDER BY Clause (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33024 is a critical server-side request forgery vulnerability in WWBN AVideo-Encoder, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33024 in the wild and no public exploit code.

Affected product: WWBN AVideo-Encoder. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-33024/ (Markdown: https://insights.sbomify.com/CVE-2026-33024/index.md)
```

## Sources

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

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