Summary
WWBN AVideo through version 29.0 does not consistently enforce user-group restrictions on Live plugin JSON endpoints. Unauthenticated attackers may retrieve restricted live transmission data, including stream keys, ownership details, and direct HLS playback URLs, when these endpoints are reachable.
Affected context
The issue occurs in AVideo deployments using the Live plugin endpoints plugin/Live/stats.json.php and plugin/Live/calendar.json.php. Risk is present where these endpoints are exposed to unauthenticated users and server-side authorization does not verify the requesting user's group membership before returning restricted transmission metadata.
Exploit preconditions
- Attack surface: HTTP-accessible Live plugin JSON endpoints
- Required access: No authentication may be required when the affected endpoints are exposed
- Trigger point: A request for live statistics or calendar data
- Why exploitation is possible: The endpoints may return restricted records without enforcing the associated user-group permissions
Why this happens
The underlying issue is an authorization failure that results in sensitive information being returned to an unauthorized requester. Endpoint-level access checks do not adequately enforce the restrictions applied to live transmissions, allowing metadata and playback-related values to cross the intended trust boundary. This maps to CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Potential impact
- Attackers may obtain live-stream keys
- Restricted titles, descriptions, or owner information could be disclosed
- Direct HLS playback URLs may be exposed
- Unauthorized users could monitor or access transmissions intended for limited groups
- Disclosed metadata could support further targeting of stream owners or infrastructure
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every endpoint that returns transmission data.
Common defensive patterns include:
- Applying server-side group and ownership checks before selecting or serializing records
- Returning only fields authorized for the requesting principal
- Using deny-by-default behavior for unauthenticated requests
- Avoiding exposure of stream keys and other access-bearing values in general-purpose JSON responses
- Separating public metadata from restricted playback and administration data
- Applying least privilege to service accounts and limiting the reach of playback URLs
- Treating client-side filtering as insufficient for access control
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis and code review checks for endpoint handlers that serialize database records without authorization checks
- Review signals showing permission validation occurs after data retrieval or response construction
- Tests that request restricted resources as anonymous and cross-group users
- API gateway or web-application policies that require authentication for sensitive Live plugin routes
- Monitoring for repeated unauthenticated requests to statistics and calendar endpoints
- Automated security review tools that identify missing access-control checks and excessive response fields

