AVideo CloneSite Flaws Enable File Deletion and Unauthenticated RCE
WWBN AVideo was found to contain multiple high-severity flaws in its CloneSite plugin that can be abused for destructive attacks and full server compromise. One issue, tracked as CVE-2026-33293, affects versions prior to 26.0 and allows arbitrary file deletion through path traversal in the deleteDump parameter of plugin/CloneSite/cloneServer.json.php. Because the value was passed directly to unlink() without sanitization, an attacker with valid clone credentials could use ../../ sequences to remove arbitrary files such as configuration.php, causing denial of service and potentially weakening other protections.
A second issue, CVE-2026-33478, describes a broader attack chain in AVideo versions up to and including 26.0 that can lead to unauthenticated remote code execution. The clones.json.php endpoint exposed clone secret keys without authentication, which could then be used to trigger a full database dump via cloneServer.json.php; the dump reportedly included admin password hashes stored as MD5, enabling attackers to recover credentials and gain administrative access. From there, an OS command injection flaw in cloneClient.json.php involving rsync command construction could be used to execute arbitrary system commands. The vulnerabilities were mapped to CWE-22, CWE-78, and CWE-284, and fixes were released by WWBN, including a patch referenced in commit c85d076375fab095a14170df7ddb27058134d38c.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
4 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-41304 published for AVideo CloneSite command injection RCE
A new CVE, CVE-2026-41304, was published for WWBN AVideo describing a remote code execution flaw in the CloneSite plugin. In version 29.0 and earlier, cloneServer.json.php built and executed a wget shell command from the unsanitized url parameter, and the issue was fixed in commit 473c609fc2defdea8b937b00e86ce88eba1f15bb.
WWBN patches AVideo unauthenticated multi-chain RCE
WWBN provided a patch for the CloneSite multi-chain remote code execution issue in commit c85d076375fab095a14170df7ddb27058134d38c. The vulnerability affected AVideo versions up to and including 26.0 and enabled unauthenticated attackers to reach OS command execution.
GitHub Security Advisories receives AVideo multi-chain RCE report
GitHub Security Advisories received a report describing a multi-step attack in AVideo's CloneSite plugin that could lead to unauthenticated remote code execution through clone key disclosure, database dump access, cracked admin hashes, and command injection.
WWBN fixes arbitrary file deletion flaw in AVideo 26.0
WWBN addressed a path traversal issue in the CloneSite plugin by releasing AVideo version 26.0. The flaw allowed authenticated users with clone credentials to use the deleteDump parameter to delete arbitrary files via unsanitized paths.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
3 references tracked. Mallory keeps watching after this page renders.
CVE-2026-41304 - WWBN AVideo vulnerable to RCE caused by clonesite plugin
cvefeed.io
Open sourceCVE-2026-33478 - AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection
cvefeed.io
Open sourceCVE-2026-33293 - AVideo Affected by Arbitrary File Deletion via Path Traversal in CloneSite deleteDump Parameter
cvefeed.io
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


