# CVE-2026-33478: AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection

> Unauthenticated attackers can achieve remote code execution by chaining clone key disclosure, database dumping, and OS command injection in the CloneSite plugin.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-687q-32c6-8x68

## What is CVE-2026-33478?

CVE-2026-33478 is a critical command injection vulnerability in Wwbn Avideo, published on 23 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 up to and including 26.0, multiple vulnerabilities in AVideo's CloneSite plugin chain together to allow a completely unauthenticated attacker to achieve remote code execution. The `clones.json.php` endpoint exposes clone secret keys without authentication, which can be used to trigger a full database dump via `cloneServer.json.php`. The dump contains admin password hashes stored as MD5, which are trivially crackable. With admin access, the attacker exploits an OS command injection in the rsync command construction in `cloneClient.json.php` to execute arbitrary system commands. Commit c85d076375fab095a14170df7ddb27058134d38c contains a patch.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-284 (Improper Access Control)

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

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

Products: Wwbn Avideo.

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

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

## Is CVE-2026-33478 being exploited?

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

Public exploit code:

- AVideo <= 26.0 - WWBN AVideo - Remote Code Execution (nuclei): http/cves/2026/CVE-2026-33478.yaml

## 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-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)
- [CVE-2026-33352](https://insights.sbomify.com/CVE-2026-33352/): AVideo has an Unauthenticated SQL Injection via `doNotShowCats` Parameter (Backslash Escape Bypass) (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33478 is a critical command injection vulnerability in Wwbn Avideo, published on 23 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-33478 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 26.0; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 26.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-33478/ (Markdown: https://insights.sbomify.com/CVE-2026-33478/index.md)
```

## Sources

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

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