CVE-2026-33478
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWWBN AVideo is an open source video platform. In versions up to and including 26.0, multiple vulnerabilities in AVideo's CloneSite plugin chain together to allow a completely unauthenticated attacker to achieve remote code execution. The `clones.json.php` endpoint exposes clone secret keys without authentication, which can be used to trigger a full database dump via `cloneServer.json.php`. The dump contains admin password hashes stored as MD5, which are trivially crackable. With admin access, the attacker exploits an OS command injection in the rsync command construction in `cloneClient.json.php` to execute arbitrary system commands. Commit c85d076375fab095a14170df7ddb27058134d38c contains a patch.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMultiple critical vulnerabilities in AVideo's CloneSite plugin chain together to achieve unauthenticated remote code execution. First, clones.json.php exposes clone secret keys without authentication. These keys enable a full database dump via cloneServer.json.php, revealing admin password hashes stored as insecure MD5. With cracked admin credentials, attackers exploit OS command injection in the rsync command construction within cloneClient.json.php to execute arbitrary system commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 26.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if CloneSite plugin is installedCheck the plugins directory for the CloneSite plugin folder, or query the plugin management interface if available in the Avideo admin panelAffected if CloneSite plugin directory exists on the server
-
Check if clones.json.php is accessible without authenticationAttempt to access /plugin/CloneSite/clones.json.php (or the equivalent path) via HTTP request without providing any credentials - the CVE indicates this endpoint exposes secret keys without authenticationAffected if The endpoint returns clone secret keys or sensitive data without requiring authentication
-
Verify if cloneServer.json.php is accessible with obtained keysIf secret keys were obtained from clones.json.php, test whether cloneServer.json.php can be accessed using those keys to dump database contentsAffected if Database dumps or admin password hashes (stored as MD5) are exposed via this endpoint
-
Confirm admin password hash storage methodExamine the user table in the database or check user configuration files to determine if admin passwords are hashed using MD5 rather than secure hashing algorithmsAffected if Admin passwords are stored as MD5 hashes
-
Check rsync command construction in cloneClient.json.phpReview the source code of cloneClient.json.php (if accessible) to identify if user-controllable input is passed directly to rsync command execution without sanitizationAffected if User input from CloneSite functionality flows into rsync command without validation, enabling command injection
-
Determine Avideo versionCheck the installed Avideo version by examining version.php, the admin dashboard, or API endpoints - compare against the affected range of <= 26.0Affected if Installed version is 26.0 or lower
The environment is affected if CloneSite plugin is installed, Avideo version is <= 26.0, and the vulnerable CloneSite endpoints are accessible without authentication, exposing secret keys that could lead to command injection via rsync.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict access to CloneSite plugin endpoints, upgrade to the patched version (commit c85d0763), migrate away from MD5 password hashing, and implement input validation on rsync command parameters.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33478 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data