# CVE-2026-63305: AVideo through 29.0 OS Command Injection via ffmpeg.json.php

> Attackers can execute arbitrary OS commands via the ffmpeg.json.php endpoint by injecting shell metacharacters into encrypted payload parameters.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 16 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-g9x9-q7qj-6mv5, GHSA-jrxj-9mhw-55wc

## What is CVE-2026-63305?

CVE-2026-63305 is a critical command injection vulnerability in WWBN AVideo, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AVideo through 29.0 contains an OS command injection vulnerability in the ffmpeg.json.php endpoint where notifyCode and callback parameters are concatenated into a shell command without escaping. Attackers who can craft a valid encrypted payload can inject arbitrary shell metacharacters into these fields to execute OS commands as the web-server user.

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

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


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

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

## Is CVE-2026-63305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63305 is a critical command injection vulnerability in WWBN AVideo, published on 16 Jul 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-63305 exists.

Affected product: WWBN AVideo. 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-63305/ (Markdown: https://insights.sbomify.com/CVE-2026-63305/index.md)
```

## Sources

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

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