Path Traversal in wwbn/avideo (CVE-2026-41058)
Summary
Path traversal in wwbn/avideo (CVE-2026-41058). Data can be tampered with by attackers. Exploitable via deleteDump.
Original description
The description as published by the source.
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['deleteDump'])) {
$resp->error = !unlink("{$clonesDir}{$_GET['deleteDump']}");
$resp->msg = "Delete Dump {$_GET['deleteDump']}";
die(json_encode($resp));
}
No basename(), no realpath() check, no path traversal filtering. $_GET['deleteDump'] 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 withmysqldumppass credentials on the command line
PoC
"""
CVE-2026-33293 - AVideo CloneSite Path Traversal
"""
import sys
import os
VULN_SRC = os.path.join(os.path.dirname(__file__), "src", "cloneServer.json.php")
def verify_source_file():
if not os.path.isfile(VULN_SRC):
print("ERROR: Source not found at %s" % VULN_SRC)
sys.exit(1)
with open(VULN_SRC, "r") as f:
src = f.read()
if "unlink(" not in src or "dele…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41058 has been found in wwbn/avideo.
Attackers can target a specific entry point like deleteDump over the network to misuse the product.
Data can be tampered with by attackers.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wwbn/avideo CVE-2026-41058" on the vendor's site.
CVE-2026-41058 (wwbn/avideo) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Attack surface: deleteDump / mysqldump / configuration.php
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in wwbn/avideo. Attackers reach the vulnerable code path via deleteDump.
Check the vendor advisory for the affected versions of wwbn/avideo. Attack surface: deleteDump / mysqldump / configuration.php.
Severity: ?. Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wwbn/avideo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wwbn/avideo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wwbn/avideoを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com