# CVE-2026-43873: AVideo: Unauthenticated Disclosure of CloneSite `myKey` via Error Echo in `cloneClient.json.php` Enables Cross-Site DB Dump of the Configured Clone Server

> Unauthenticated attackers can leak the CloneSite shared secret via error messages, enabling database dumps from configured remote clone servers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-qm9p-p5pw-jrx2

## What is CVE-2026-43873?

CVE-2026-43873 is a high-severity vulnerability in WWBN AVideo, published on 11 May 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 29.0, plugin/CloneSite/cloneClient.json.php echoes the local CloneSite shared secret ($objClone->myKey, a constant md5($global['systemRootPath'] . $global['salt'])) into the HTTP response body on every unauthenticated request. The unauthenticated error branch was intended to reject non-admin callers without a valid key, but the rejection message interpolates the expected key before die(). When the victim has CloneSite configured with a remote cloneSiteURL (standard federation/backup setup), the leaked myKey is exactly the credential that authenticates the victim to that remote server's cloneServer.json.php, allowing the attacker to impersonate the victim and trigger a full mysqldump of the remote's database to the remote's public videos/clones/ directory Commit e6566f56a28f4556b2a0a09d03717a719dcb49da contains an updated fix.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

2 open source packages ship an affected version, including wwbn/avideo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wwbn/avideo` | Packagist | All versions to 29.0 | None |
| `wwbn/avideo` | Packagist | All versions to 29.0 | None |

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

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

## Is CVE-2026-43873 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-43873 is a high-severity vulnerability in WWBN AVideo, published on 11 May 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-43873 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-43873/ (Markdown: https://insights.sbomify.com/CVE-2026-43873/index.md)
```

## Sources

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

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