SSRF (Server-Side Request Forgery) in WWBN/AVideo (CVE-2026-39370)
Summary
SSRF in WWBN/AVideo (CVE-2026-39370). Confidential information can be exposed externally. Exploitable via POST /objects/aVideoEncoder.json.php.
Original description
The description as published by the source.
Summary
The fix for CVE-2026-27732 is incomplete.
objects/aVideoEncoder.json.php still allows attacker-controlled downloadURL values with common media or archive extensions such as .mp4, .mp3, .zip, .jpg, .png, .gif, and .webm to bypass SSRF validation. The server then fetches the response and stores it as media content.
This allows an authenticated uploader to turn the upload-by-URL flow into a reliable SSRF response-exfiltration primitive.
Details
objects/aVideoEncoder.json.php accepts attacker-controlled downloadURL and passes it to downloadVideoFromDownloadURL().
Inside that function:
- the URL extension is extracted from the attacker-controlled path
- the extension is checked against an allowlist of normal encoder formats
isSSRFSafeURL()is skipped for common media and archive extensions- the URL is fetched via
url_get_contents() - the fetched body is written into video storage and exposed through normal media metadata
The current code still contains:
- an extension-based bypass for SSRF validation
- no mandatory initial-destination SSRF enforcement inside
url_get_contents()itself
This means internal URLs such as:
http://127.0.0.1:9998/probe.mp4
remain reachable from the application host.
This issue is best described as an incomplete fix / patch bypass of CVE-2026-27732, not a separate unrelated SSRF class.
Proof of concept
- Log i…
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-39370 has been found in WWBN/AVideo.
Attackers can target a specific entry point like POST /objects/aVideoEncoder.json.php over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WWBN/AVideo CVE-2026-39370" on the vendor's site.
CVE-2026-39370 (WWBN/AVideo) — CWE-918 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /objects/aVideoEncoder.json.php / GET /objects/videos.json.php / downloadURL / videos_id
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 /objects/aVideoEncoder.json.php.
Check the vendor advisory for the affected versions of WWBN/AVideo. Attack surface: POST /objects/aVideoEncoder.json.php / GET /objects/videos.json.php / downloadURL / videos_id.
Severity: High (CVSS 7.1/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 /objects/aVideoEncoder.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 /objects/aVideoEncoder.json.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /objects/aVideoEncoder.json.phpへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /objects/aVideoEncoder.json.php on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com