# CVE-2023-32073: AVideo command injection vulnerability

> Remote attackers can execute arbitrary commands on AVideo installations if the CloneSite plugin is enabled, leading to full system compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2023
- **Updated:** 23 Jan 2025
- **Also known as:** GHSA-2mhh-27v7-3vcx

## What is CVE-2023-32073?

CVE-2023-32073 is a high-severity command injection vulnerability in Wwbn Avideo, published on 12 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. In versions 12.4 and prior, a command injection vulnerability exists at `plugin/CloneSite/cloneClient.json.php` which allows Remote Code Execution if you CloneSite Plugin. This is a bypass to the fix for CVE-2023-30854, which affects WWBN AVideo up to version 12.3. This issue is patched in commit 1df4af01f80d56ff2c4c43b89d0bac151e7fb6e3.

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

## Which versions are affected by CVE-2023-32073?

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

Products: Wwbn Avideo.

## How do I fix CVE-2023-32073?

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

## Is CVE-2023-32073 being exploited?

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

Public exploit code:

- WWBN AVideo Authenticated RCE (github_poc): https://github.com/jmrcsnchz/CVE-2023-32073

## 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-2023-32073 and fix it if it is affected.

What it is: CVE-2023-32073 is a high-severity command injection vulnerability in Wwbn Avideo, published on 12 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32073 exists.

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

## Sources

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

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