# CVE-2026-33237: AVideo has SSRF in Scheduler Plugin via callbackURL Missing `isSSRFSafeURL()` Validation

> An admin can configure a scheduled task with an internal callback URL to perform Server-Side Request Forgery against internal services or cloud metadata.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-v467-g7g7-hhfh

## What is CVE-2026-33237?

CVE-2026-33237 is a medium-severity server-side request forgery vulnerability in Wwbn Avideo, published on 20 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. Prior to version 26.0, the Scheduler plugin's `run()` function in `plugin/Scheduler/Scheduler.php` calls `url_get_contents()` with an admin-configurable `callbackURL` that is validated only by `isValidURL()` (URL format check). Unlike other AVideo endpoints that were recently patched for SSRF (GHSA-9x67-f2v7-63rw, GHSA-h39h-7cvg-q7j6), the Scheduler's callback URL is never passed through `isSSRFSafeURL()`, which blocks requests to RFC-1918 private addresses, loopback, and cloud metadata endpoints. An admin can configure a scheduled task with an internal network `callbackURL` to perform SSRF against cloud infrastructure metadata services or internal APIs not otherwise reachable from the internet. Version 26.0 contains a patch for the issue.

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

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

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 | 26.0 |
| `wwbn/avideo` | Packagist | All versions | 26.0 |

Products: Wwbn Avideo.

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

Upgrade wwbn/avideo to 26.0 or later.

## Is CVE-2026-33237 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33237 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-33237 and fix it if it is affected.

What it is: CVE-2026-33237 is a medium-severity server-side request forgery vulnerability in Wwbn Avideo, published on 20 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33237 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions; fixed in 26.0
- wwbn/avideo (Packagist): affected all versions; fixed in 26.0

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

## Sources

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

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