OS Command Injection in wwbn/avideo (CVE-2026-41064)
Summary
OS command injection in wwbn/avideo (CVE-2026-41064). Confidential information can be exposed externally. Exploitable via test.php.
Original description
The description as published by the source.
Summary
The incomplete fix for AVideo's test.php adds escapeshellarg for wget but leaves the file_get_contents and curl code paths unsanitized, and the URL validation regex /^http/ accepts strings like httpevil.com.
Affected Package
- Ecosystem: Other
- Package: AVideo
- Affected versions: < commit 1e6cf03e93b5
- Patched versions: >= commit 1e6cf03e93b5
Details
The vulnerable wget() function in plugin/Live/test.php:
function wget($url, $filename) {
$cmd = "wget --tries=1 {$url} -O {$filename} --no-check-certificate";
exec($cmd);
}
Neither $url nor $filename is passed through escapeshellarg(). The URL validation uses preg_match("/^http/", $url) which:
- Does not require
://(matcheshttpevil.com) - Does not block shell metacharacters (
;, backticks,$()) - Does not validate the URL is actually a URL
A payload like http://x; id > /tmp/pwned; echo passes the regex and injects arbitrary commands via the semicolons.
The fix adds escapeshellarg() for the wget path and an isAllowedStatsTestURL allowlist, but url_get_contents() (used by the same endpoint) still follows redirects without validation. The wget-specific fix does not protect the file_get_contents and curl code paths that handle the same user-supplied URL.
PoC
"""
CVE-2026-33502 - Command injection in AVideo plugin/Live/test.php
Tests REAL vulnerable code from:
plugin/Live/test.php (commit pre-1e6cf03)
Th…
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-41064 has been found in wwbn/avideo.
Attackers can target a specific entry point like test.php over the network to misuse the product.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wwbn/avideo CVE-2026-41064" on the vendor's site.
CVE-2026-41064 (wwbn/avideo) — CWE-78
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: test.php / escapeshellarg / file_get_contents / curl
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.
OS command injection (CWE-78) exists in wwbn/avideo. Attackers reach the vulnerable code path via test.php without authentication.
Check the vendor advisory for the affected versions of wwbn/avideo. Attack surface: test.php / escapeshellarg / file_get_contents / curl.
Severity: ?. Confidential information can be exposed externally.
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