# CVE-2026-41304: WWBN AVideo vulnerable to RCE caused by clonesite plugin

> Attackers can execute arbitrary shell commands on the server via the CloneSite plugin's cloneServer.json.php endpoint due to unsanitized input in wget commands.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-xr6f-h4x7-r6qp

## What is CVE-2026-41304?

CVE-2026-41304 is a high-severity command injection vulnerability in Wwbn Avideo, published on 21 Apr 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 29.0 and below, the `cloneServer.json.php` endpoint in the CloneSite plugin constructs shell commands using user-controlled input (`url` parameter) without proper sanitization. The input is directly concatenated into a `wget` command executed via `exec()`, allowing command injection. An attacker can inject arbitrary shell commands by breaking out of the intended URL context using shell metacharacters (e.g., `;`). This leads to Remote Code Execution (RCE) on the server. Commit 473c609fc2defdea8b937b00e86ce88eba1f15bb contains a fix.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

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

Products: Wwbn Avideo.

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

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

## Is CVE-2026-41304 being exploited?

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

What it is: CVE-2026-41304 is a high-severity command injection vulnerability in Wwbn Avideo, published on 21 Apr 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-41304 exists.

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

## Sources

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

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