Summary
WWBN AVideo can issue authorization tokens to unauthenticated visitors without binding those tokens to a user identity or intended purpose. An attacker may obtain a token from the Gallery endpoint and reuse it against other subsystems to access restricted video content.
Affected context
The vulnerability occurs in AVideo deployments where the Gallery sections endpoint issues tokens to unauthenticated visitors and other subsystems accept those tokens for authorization decisions. Risk increases when tokens generated for one operation are treated as generally valid without verification of the requesting identity, intended action, or resource scope.
Exploit preconditions
- Attack surface: Publicly reachable AVideo Gallery and video-serving endpoints
- Required access: Network access to the affected application; authentication may not be required
- Trigger point: Token issuance through
plugin/Gallery/view/sections.php, followed by token use in another subsystem such asview/hls.php - Why exploitation is possible: Tokens are not adequately bound to a user identity or purpose, allowing a token obtained in one context to satisfy authorization checks in another
Why this happens
The underlying bug is an authorization design failure in which a token is treated as sufficient proof of permission without binding it to the identity, operation, or resource for which it was issued. The token-generation behavior permits unauthenticated issuance, while consuming endpoints accept the token across security contexts. This represents an information exposure risk under CWE-200 because authorization controls can be bypassed to disclose restricted content.
Potential impact
- An attacker may access video content intended for authorized users
- Restricted media URLs or streams could be disclosed
- The application may lose effective separation between public and protected content
- Exposed content could support privacy violations or further reconnaissance
General mitigation guidance
Mitigation generally centers on making authorization decisions independently
verifiable at every consuming endpoint.
Common defensive patterns include:
- Bind tokens cryptographically and semantically to the authenticated subject, permitted action, and target resource
- Require authentication and explicit authorization before issuing tokens for protected operations
- Reject tokens outside their intended endpoint, purpose, scope, or lifetime
- Validate authorization server-side at each resource access rather than trusting token possession alone
- Use narrowly scoped, short-lived tokens with replay protections where appropriate
- Apply least privilege to media access and avoid exposing predictable or reusable resource references
- Treat unauthenticated endpoints as public by design and ensure they cannot mint credentials for protected actions
How teams detect issues like this
Detection can combine code review, automated analysis, and runtime monitoring.
- Search for token-generation functions that omit subject, audience, purpose, resource, expiry, or scope claims
- Review endpoints that accept tokens without independently checking identity and requested resource authorization
- Trace whether tokens issued by public endpoints are accepted by unrelated protected subsystems
- Add static-analysis or policy rules for authorization checks based solely on token presence
- Test endpoint combinations with anonymous sessions and tokens obtained from public workflows
- Monitor unusual access to protected media following token issuance from unauthenticated requests

