SSRF (Server-Side Request Forgery) in wwbn/avideo (CVE-2026-43884)
Summary
SSRF in wwbn/avideo (CVE-2026-43884). Confidential information can be exposed externally. Exploitable via POST /plugin/AI/receiveAsync.json.php.
Original description
The description as published by the source.
WWBN AVideo is an open source video platform. In versions up to and including 29.0, two endpoints (plugin/AI/receiveAsync.json.php and objects/EpgParser.php) in AVideo call isSSRFSafeURL() to validate user-supplied URLs, then fetch them using bare file_get_contents() without disabling PHP's automatic redirect following. An attacker can supply a URL pointing to a server they control that returns a 302 redirect to an internal/cloud-metadata address (e.g., http://169.254.169.254/latest/meta-data/). Since isSSRFSafeURL() only validates the initial URL, the redirect target bypasses all SSRF protections. Commit 603e7bf77a835584387327e35560262feb075db3 contains an updated fix.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-43884 has been found in wwbn/avideo.
Attackers can target a specific entry point like POST /plugin/AI/receiveAsync.json.php over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "wwbn/avideo CVE-2026-43884" on the vendor's site.
CVE-2026-43884 (wwbn/avideo) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /plugin/AI/receiveAsync.json.php / follow_location / CURLOPT_RESOLVE / isSSRFSafeURL
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 POST /plugin/AI/receiveAsync.json.php.
Check the vendor advisory for the affected versions of wwbn/avideo. Attack surface: POST /plugin/AI/receiveAsync.json.php / follow_location / CURLOPT_RESOLVE / isSSRFSafeURL.
Severity: High (CVSS 7.7/10). 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 POST /plugin/AI/receiveAsync.json.php requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /plugin/AI/receiveAsync.json.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /plugin/AI/receiveAsync.json.phpへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /plugin/AI/receiveAsync.json.php on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- report github.com
- web github.com