Summary
WWBN AVideo contains a cross-site request forgery vulnerability in the releaseVideoNow.json.php endpoint because it accepts state-changing GET requests without verifying request authenticity. If an administrator is authenticated, an attacker may cause the administrator's browser to permanently publish an embargoed video by inducing a request containing a chosen videos_id value.
Affected context
The vulnerability occurs in AVideo deployments where the video-release endpoint is accessible through an administrator's authenticated browser session. Risk is increased when the endpoint accepts GET requests, relies on ambient session cookies, and does not require an anti-CSRF token or equivalent origin validation before changing publication state.
Exploit preconditions
- Attack surface: The
releaseVideoNow.json.phpHTTP endpoint - Required access: The victim must have an authenticated administrator session with permission to publish videos
- Trigger point: A cross-site request targeting the endpoint with a selected
videos_idvalue - Why exploitation is possible: The application accepts a state-changing GET request and does not verify that it originated from the trusted application
Why this happens
The underlying bug is a failure to distinguish trusted application requests from cross-site requests. A state-changing endpoint accepts a browser-supplied session cookie without requiring an unpredictable request token, validating the request origin, or using another authenticity mechanism. This behavior maps to CWE-352: Cross-Site Request Forgery, where an attacker can cause an authenticated user agent to perform an unintended action.
Potential impact
- An attacker may permanently publish embargoed videos
- Unauthorized content changes could occur under an administrator's account
- Publication timing and editorial controls could be bypassed
- The affected account's audit trail may attribute the action to the administrator
General mitigation guidance
Mitigation typically focuses on protecting every state-changing action from cross-site request forgery and reducing reliance on ambient browser credentials.
Common defensive patterns include:
- Requiring anti-CSRF tokens for authenticated state-changing requests
- Using POST or another semantically appropriate method for mutations rather than GET
- Validating trusted origin or referrer signals as a defense-in-depth control
- Applying restrictive, appropriate cookie attributes such as SameSite
- Requiring explicit authorization and least privilege for publication operations
- Avoiding state changes when request authenticity cannot be established
How teams detect issues like this
Organizations commonly detect CSRF risks through:
- Static analysis rules identifying state changes in GET handlers
- Code review checks for missing CSRF middleware, tokens, or origin validation
- Endpoint inventories that classify authenticated routes by HTTP method and side effect
- Dynamic testing that submits cross-origin requests against authenticated workflows
- Policy enforcement requiring CSRF protections for browser-accessible mutation endpoints
Automated security review tools may help identify handlers that modify publication state without an authenticity check.

