/

CVE-2026-92582

Severity:

HIGH RISK

(7.1)

Cross-Site Request Forgery (CWE-352) in AVideo API

CVE-2026-92582

Deferred

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352

Impact:

Unauthorized modification of video content and access controls

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

AVideo contains a cross-site request forgery vulnerability in the video-management request handler because CSRF and same-origin protections can be bypassed when attacker-controlled request parameters are present. If an authenticated user with video-management permissions visits a malicious page, the attacker may cause the user's browser to submit unauthorized changes to video records.

Affected context

The issue occurs in AVideo deployments through the affected code path when the video-management endpoint accepts request parameters from $_REQUEST and treats the presence of user and pass values as sufficient to disable defensive checks. Risk is greatest when authenticated users with upload, administrative, or video-management permissions can be induced to visit attacker-controlled content.

Exploit preconditions

  • Attack surface: AVideo's video-management HTTP endpoint
  • Required access: A victim must be authenticated in the browser and possess permissions to modify videos
  • Attacker capability: Ability to host or deliver a crafted cross-origin page or request
  • Trigger point: Processing of a state-changing video-management request
  • Why exploitation is possible: The endpoint conditionally disables CSRF and same-origin protections based on the presence of unvalidated request parameters, while an existing authenticated session can satisfy the login state check

Why this happens

The vulnerability results from treating the presence of attacker-controlled authentication parameters as proof that a request is trusted. The handler reads these values from a broad request source, disables CSRF and same-origin defenses, and does not require the submitted credentials to be valid before accepting the request. This is a cross-site request forgery weakness mapped to CWE-352, in which a state-changing operation relies on ambient browser authentication without requiring a request-specific authenticity token or equivalent origin validation.

Potential impact

  • An attacker could cause unauthorized changes to video metadata
  • Video ownership or access restrictions could be modified
  • Private-content protections could be weakened or removed
  • Download, sharing, payment, password, rating, status, or view-count settings could be altered
  • An attacker could delete or change group-based access controls
  • Administrative users could expose or disrupt videos across the site

General mitigation guidance

Mitigation generally focuses on preserving CSRF and same-origin protections for every state-changing operation.

Common defensive patterns include:

  • Requiring unpredictable, session-bound CSRF tokens for state-changing requests
  • Validating the request origin or referer as a complementary control where appropriate
  • Avoiding security decisions based solely on the presence of query or form parameters
  • Restricting authentication inputs to explicit, validated channels rather than broad request collections
  • Using safe-by-default middleware that rejects missing or invalid CSRF tokens
  • Applying authorization checks to every modified object and sensitive field
  • Limiting administrative privileges and separating video-editing permissions from broader site administration
  • Configuring cookies with appropriate SameSite, Secure, and HttpOnly attributes as defense in depth

How teams detect issues like this

High-level detection approaches include:

  • Static analysis for state-changing handlers that read from $_REQUEST or equivalent mixed input sources
  • Code review searches for CSRF checks that can be disabled by user-controlled flags or parameter presence
  • Identifying endpoints that modify records without requiring a request-specific token
  • Testing cross-origin requests in authorized security assessments to confirm that browser credentials are not accepted without CSRF validation
  • Monitoring audit logs for unusual bulk changes to ownership, privacy, sharing, or access-control fields
  • Enforcing secure coding policies requiring CSRF protection on all cookie-authenticated state-changing routes

Automated security review tools may help identify missing or conditionally bypassed CSRF defenses, but findings should be validated against application authorization behavior.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-qf9p-jhx7-rhmf
vulncheck.comvulncheck.com/advisories/avideo-through-29.0-broken-access-control-via-videoaddnew-json-php-csrf-bypass

Frequently asked

questions

Yes, in the browser-based sense. An attacker may host or deliver a cross-origin page, but successful impact generally depends on a victim who is authenticated to AVideo and has permissions to perform the targeted action.

No. The attack can rely on the victim's existing authenticated session cookie; the presence of attacker-supplied request parameters is not equivalent to valid credential verification.

Require a valid, session-bound CSRF token for every state-changing request and retain same-origin protections. Security controls should not be disabled merely because request parameters are present.

Apply centralized CSRF middleware, use explicit input sources, validate origin and authorization independently, configure secure cookie attributes, and include cross-origin request tests in code review and security testing.

Find out what's already
exploitable in your codebase.