# CVE-2026-92580: AVideo through 29.0 CloneSite Stored Shell Injection via SSH Password CSRF

> An attacker can achieve remote code execution as root or www-data by injecting shell commands via a stored SSH password in the AVideo CloneSite plugin, exploiting a CSRF vulnerability.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-c9w6-444r-27pj, GHSA-g96r-pgr6-m7hh

## What is CVE-2026-92580?

CVE-2026-92580 is a high-severity command injection vulnerability in WWBN AVideo, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In AVideo through 29.0, the CloneSite plugin is vulnerable to stored OS command injection. In plugin/CloneSite/cloneClient.json.php (line ~270) the stored SSH password is substituted into the command string `sshpass -p '{password}' rsync ...` with a plain str_replace and no escaping, so a single quote in the password breaks out of the quoted word and injects arbitrary shell. The password is written through the admin-only endpoint objects/pluginAddDataObject.json.php, whose only CSRF defense (isUntrustedRequest()/forbidIfIsUntrustedRequest()) is a no-op when the request source appears to be loopback — as happens behind a same-host TLS-terminating reverse proxy with $global['trustedProxies'] unset — or when an attacker-controlled application is co-hosted on the same hostname; on HTTPS the session cookie is issued with SameSite=None, so a cross-site POST carries it. An unauthenticated remote attacker can therefore lure an authenticated administrator into planting a malicious password (and an attacker-controlled cloneSiteURL), after which the plugin's documented crontab entry executes the injected command with no further administrator action, as the crontab owner (commonly root or www-data). Exploitation requires the CloneSite plugin to be enabled with the documented crontab installed and one of the above CSRF channels; default single-process Apache deployments are reported as not CSRF-exploitable. This is a residual sink of CVE-2026-41304. The issue is confirmed at master HEAD (8963b6a1); no patched version is available.

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

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


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

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

## Is CVE-2026-92580 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92580 is a high-severity command injection vulnerability in WWBN AVideo, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92580 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-92580/ (Markdown: https://insights.sbomify.com/CVE-2026-92580/index.md)
```

## Sources

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

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