How severe is GHSA-q4x6-6mm2-crg9?

GHSA-q4x6-6mm2-crg9 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-q4x6-6mm2-crg9?

GHSA-q4x6-6mm2-crg9 affects the following packages: WWBN/AVideo (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-q4x6-6mm2-crg9?

No patched version of WWBN/AVideo has shipped for GHSA-q4x6-6mm2-crg9 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-q4x6-6mm2-crg9 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for WWBN/AVideo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q4x6-6mm2-crg9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-q4x6-6mm2-crg9?

O3 pinpoints whether GHSA-q4x6-6mm2-crg9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q4x6-6mm2-crg9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q4x6-6mm2-crg9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-q4x6-6mm2-crg9?

GHSA-q4x6-6mm2-crg9 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-q4x6-6mm2-crg9 published, and has it been updated?

GHSA-q4x6-6mm2-crg9 was published on April 8, 2026 and was last updated on May 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-q4x6-6mm2-crg9

MEDIUM

GHSA-q4x6-6mm2-crg9 is a medium-severity (CVSS 6.5) Server-Side Request Forgery (SSRF) vulnerability in WWBN/AVideo. O3 Security confirms whether GHSA-q4x6-6mm2-crg9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

WWBN AVideo has a Live restream log callback flow enabling stored SSRF to internal services

Also known asCVE-2026-39368

Published

Apr 8, 2026

Updated

May 26, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐘WWBN/AVideo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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:

plugin/Live/view/getRestream.json.php exposed a fresh tokenForAction
plugin/Live/view/Live_restreams/verifyTokenForAction.json.php exchanged it for a valid responseToken
plugin/Live/view/Live_restreams_logs/add.json.php accepted attacker-controlled restreamerURL
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

Log in as a non-admin user with streaming permission.
Create a normal restream destination.
Trigger plugin/Live/view/Live_restreams/testRestreamer.json.php to create a live transmission history row.
Call:

GET /plugin/Live/view/getRestream.json.php?live_transmitions_history_id=<id>&restreams_id=<id>

Extract tokenForAction from the returned URL.
Exchange it for responseToken via:

POST /plugin/Live/view/Live_restreams/verifyTokenForAction.json.php

Store a loopback callback URL:

POST /plugin/Live/view/Live_restreams_logs/add.json.php
restreamerURL=http://127.0.0.1:9999/index.php

Trigger getRestream.json.php again.
Observe that the returned response now contains the JSON body from the loopback-only service.

Impact

An authenticated streamer can cause the AVideo server to send HTTP requests to loopback or internal services and return the response through normal application endpoints by storing a malicious restreamerURL in the restream log flow. Because the callback destination was not constrained to trusted restreamer endpoints, the application could be used as a proxy to internal-only services that trust network locality. Successful exploitation can expose local admin panels, internal-only APIs, cloud metadata services if reachable, or other sensitive internal responses available from the application host.

Recommended fix

Validate restreamerURL against explicitly configured restreamer endpoints at storage time
Re-validate the stored callback URL before server-side fetch
Bind responseToken to the expected restream row and callback host
Apply SSRF validation to the initial destination of every server-side fetch, not only redirect targets
Ignore or reject user-supplied callback hosts that do not match trusted configuration

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`WWBN/AVideo`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for WWBN/AVideo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of WWBN/AVideo has shipped for GHSA-q4x6-6mm2-crg9 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-q4x6-6mm2-crg9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q4x6-6mm2-crg9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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` exchange

O3 Security · Impact-Aware SCA

Is GHSA-q4x6-6mm2-crg9 in your dependencies?

O3 detects GHSA-q4x6-6mm2-crg9 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works