Summary
WWBN AVideo's standalone live stream control endpoint trusts a user-supplied streamerURL parameter to decide where to send token verification requests.
By pointing streamerURL to an attacker-controlled server that always reports successful verification, an attacker can completely bypass authentication and gain unauthorized control over live stream operations.
Affected context
This vulnerability occurs in WWBN AVideo installations using the Live plugin's standalone control endpoint:
- Endpoint:
plugin/Live/standAloneFiles/control.json.php - Authentication for live stream actions depends on a token verification request sent to a URL derived from the
streamerURLparameter. - The application implicitly trusts
streamerURLinput without constraining it to trusted origins.
Environments where this endpoint is reachable to untrusted users and where live stream management relies on remote token validation are at risk.
Exploit preconditions
- Attack surface: HTTP(S) access to
plugin/Live/standAloneFiles/control.json.php. - Required access: Network access to the AVideo web interface; no prior authentication is required if the endpoint is publicly exposed.
- Trigger point: Sending crafted requests to the control endpoint with a
streamerURLparameter pointing to an attacker-controlled verification server. - Why exploitation is possible: The server blindly trusts the token verification response from the caller-supplied
streamerURLand treats any{"error": false}response as proof of successful authentication, with no origin validation or server-side enforcement of a fixed verification endpoint.
Why this happens
The core issue is an authentication design that relies on externally supplied URLs for security decisions.
Instead of using a server-controlled, fixed verification endpoint, the application allows the client to dictate streamerURL, which determines where token verification is sent.
This maps to CWE-287: Improper Authentication, because the system bases authentication solely on a response from an untrusted endpoint chosen by the user, effectively allowing attackers to self-approve requests by operating a verification service that always signals success.
Conceptually, this is a form of confused deputy combined with trusting user-controlled endpoints for security checks.
Potential impact
- Attackers can gain unauthenticated control over any live stream's management interface.
- Active publishers may be forcibly dropped from their live streams.
- Recording sessions can be started, stopped, or disrupted without authorization.
- Attackers can probe for the existence or status of live streams, aiding enumeration and surveillance.
- Service instability or denial of service for streamers due to malicious manipulation of live stream controls.
General mitigation guidance
Effective mitigation focuses on removing user control over security-critical verification endpoints and tightening authentication flows:
- Use a fixed, server-side configuration for token verification URLs; do not allow clients to override or influence these URLs via request parameters.
- Enforce strict origin and host validation for any external calls involved in authentication or authorization decisions.
- Treat any user-provided URLs or endpoints as untrusted data and never as authorities on authentication outcomes.
- Introduce layered authorization checks on live stream control actions, ensuring that even with a successful token check, additional server-side permissions are validated.
- Minimize exposure of powerful management endpoints by placing them behind authenticated sessions, API keys, or dedicated access control mechanisms.
- Apply least privilege to live control operations so that even compromised flows cannot affect all streams by default.
How teams detect issues like this
Detection and assurance can use a mix of code review and automated analysis:
- Code review signals:
- Authentication or authorization logic that accepts URLs, callbacks, or hosts from request parameters or query strings.
- Use of user-controlled data when constructing token verification or identity provider endpoints.
- Security decisions delegated to remote servers whose location is influenced by client input.
- Static analysis patterns:
- Rules that flag external HTTP requests (
curl,file_get_contents, HTTP client libraries) where the target URL is directly derived from request parameters in authentication-related modules. - Identification of conditions where an
errororsuccessfield from a remote response is used to gate access without additional verification. - Policy and testing approaches:
- Security tests that attempt to replace verification endpoints with attacker-controlled URLs and observe whether access is granted.
- CI pipelines that enforce policies such as "no user-controlled URL in auth/verification code paths."
- Automated code scanning tools can be configured with custom rules to flag user-influenced endpoints in sensitive authentication logic.

