Categories
CVE-2026-39368 medium CVSS 6.5

SSRF (Server-Side Request Forgery) in WWBN/AVideo (CVE-2026-39368)

Summary

SSRF in WWBN/AVideo (CVE-2026-39368). Confidential information can be exposed externally. Exploitable via GET /plugin/Live/view/getRestream.json.php.

Original description

The description as published by the source.

Summary

The Live restream log callback flow accepted an attacker-controlled restreamerURL and later fetched that stored URL server-side, enabling stored SSRF for authenticated streamers.

The vulnerable flow allowed a low-privilege user with streaming permission to store an arbitrary callback URL and trigger server-side requests to loopback or internal HTTP services through the restream log feature.

Details

The vulnerable chain was:

  1. plugin/Live/view/getRestream.json.php exposed a fresh tokenForAction
  2. plugin/Live/view/Live_restreams/verifyTokenForAction.json.php exchanged it for a valid responseToken
  3. plugin/Live/view/Live_restreams_logs/add.json.php accepted attacker-controlled restreamerURL
  4. plugin/Live/view/getRestream.json.php and plugin/Live/view/Live_restreams/getAction.json.php later fetched that stored URL server-side

The original issue existed because the responseToken was accepted, but the callback destination was not tightly constrained to trusted restreamer endpoints.

The maintainer confirmed the vulnerability and stated that the fix was applied by validating restreamerURL at storage time and re-validating the log-entry branch before use. The maintainer also noted that the m3u8 field follows the same general pattern but is not server-fetched in the current flow.

Proof of concept

  1. Log in as a non-admin user with streaming permission.
  2. Create a normal restream destination.
  3. Trigger `plugin/Live/view/Live_restre…

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-39368 has been found in WWBN/AVideo.
Attackers can target a specific entry point like GET /plugin/Live/view/getRestream.json.php over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WWBN/AVideo CVE-2026-39368" on the vendor's site.

CVE-2026-39368 (WWBN/AVideo) — CWE-918 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /plugin/Live/view/getRestream.json.php / POST /plugin/Live/view/Live_restreams/verifyTokenForAction.json.php / POST /plugin/Live/view/Live_restreams_logs/add.json.php / restreamerURL
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.

❓ What is the problem

SSRF (CWE-918) exists in WWBN/AVideo. Attackers reach the vulnerable code path via GET /plugin/Live/view/getRestream.json.php.

📍 Affected scope

Check the vendor advisory for the affected versions of WWBN/AVideo. Attack surface: GET /plugin/Live/view/getRestream.json.php / POST /plugin/Live/view/Live_restreams/verifyTokenForAction.json.php / POST /plugin/Live/view/Live_restreams_logs/add.json.php / restreamerURL.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /plugin/Live/view/getRestream.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

  1. 1
    Identify exposure identify
    grep -r 'WWBN/AVideo' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で WWBN/AVideo を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'GET /plugin/Live/view/getRestream.json.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /plugin/Live/view/getRestream.json.php への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify
    Replay attack against GET /plugin/Live/view/getRestream.json.php on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Packagist WWBN/AVideo
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"26.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details