SSRF (Server-Side Request Forgery) in wwbn/avideo (CVE-2026-33502)
Summary
SSRF in wwbn/avideo (CVE-2026-33502). Confidential information can be exposed externally. Exploitable via http.
Original description
The description as published by the source.
Summary
An unauthenticated server-side request forgery vulnerability in plugin/Live/test.php allows any remote user to make the AVideo server send HTTP requests to arbitrary URLs. This can be used to probe localhost/internal services and, when reachable, access internal HTTP resources or cloud metadata endpoints.
Details
The endpoint accepts $_REQUEST['statsURL'] and only checks that it starts with http:
$statsURL = $_REQUEST['statsURL'];
if (empty($statsURL) || $statsURL == "php://input" || !preg_match("/^http/", $statsURL)) {
exit;
}
It then calls:
$result = url_get_contents($statsURL, 2);
Inside the same file, url_get_contents() performs a real outbound request with file_get_contents() when allow_url_fopen is enabled:
$tmp = file_get_contents($url, false, $context);
_log('file_get_contents:: '.htmlentities($tmp));
There is:
- no authentication check
- no allowlist of trusted stats URLs
- no SSRF-safe URL validation
- reflected response/error output
Validated on source:
PoC
Target used during validation:
http://127.0.0.1:80
- Probe a closed localhost port:
curl -s \
'http://127.0.0.1:80/plugin/Live/test.php?statsURL=http://127.0.0.1:1/'
Observed response excerpt:
Starting try to get URL http://127.0.0.1:1/
url_get_contents start timeout=2
Warning: file_g…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33502 has been found in wwbn/avideo.
Attackers can target a specific entry point like http over the network to misuse the product.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wwbn/avideo CVE-2026-33502" on the vendor's site.
CVE-2026-33502 (wwbn/avideo) — CWE-918
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: http / allow_url_fopen / wget / file_get_contents
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in wwbn/avideo. Attackers reach the vulnerable code path via http without authentication.
Check the vendor advisory for the affected versions of wwbn/avideo. Attack surface: http / allow_url_fopen / wget / file_get_contents.
Severity: ?. Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wwbn/avideo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wwbn/avideo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wwbn/avideoを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com