/

CVE-2026-83595

Severity:

HIGH RISK

(8.1)

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

CVE-2026-83595

Deferred

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352

Impact:

Unauthorized state-changing actions

Severity:

HIGH RISK

(8.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 plugin/API/set.json.php, where state-changing API actions can be triggered through crafted GET requests that bypass CSRF protections. If an authenticated user visits or is directed to a malicious URL, an attacker may cause actions such as deleting videos, deactivating accounts, or modifying playlists.

Affected context

The vulnerability occurs in AVideo deployments that expose the plugin/API/set.json.php endpoint and accept state-changing operations through GET requests without sufficiently binding requests to the user's intended session. Risk depends on the endpoint's authentication behavior, browser cookie handling, and whether a victim with relevant privileges can be induced to load an attacker-controlled URL.

Exploit preconditions

  • Attack surface: The AVideo plugin/API/set.json.php API endpoint
  • Required access: A victim must be authenticated and have permissions for the targeted action
  • Trigger point: A crafted URL causes the victim's browser to submit a state-changing GET request
  • Why exploitation is possible: The endpoint accepts state-changing requests without an effective CSRF token or equivalent request-origin validation

Why this happens

The underlying bug is a failure to distinguish intentionally submitted state-changing requests from cross-origin requests sent by a third-party site. Allowing GET requests to perform mutations while relying on ambient authentication cookies, without a robust anti-CSRF mechanism, maps to CWE-352: Cross-Site Request Forgery.

Potential impact

  • An attacker may delete videos associated with the victim's account or accessible resources.
  • An attacker could deactivate user accounts when the victim has sufficient privileges.
  • An attacker may modify playlists or other persisted application state.
  • The vulnerability can cause unauthorized administrative or content-management actions.

General mitigation guidance

Mitigation generally focuses on ensuring that state-changing operations cannot

be performed through unsafe cross-origin request patterns.

Common defensive patterns include:

  • Requiring POST, PUT, PATCH, or DELETE semantics for state-changing operations rather than GET.
  • Enforcing unpredictable, session-bound CSRF tokens on every mutating request.
  • Validating trusted Origin or Referer signals as a defense-in-depth control.
  • Applying appropriate SameSite cookie settings while not treating them as the sole protection.
  • Reducing endpoint privileges and requiring explicit authorization for destructive actions.
  • Using confirmation and reauthentication controls for especially sensitive operations.

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag state-changing behavior behind GET routes.
  • Code review checks for missing CSRF tokens, origin validation, or unsafe reliance on browser cookies.
  • API tests that submit cross-origin requests to mutating endpoints and verify rejection.
  • Policy enforcement requiring anti-CSRF middleware for authenticated state-changing routes.
  • Monitoring for unusual bursts of deletion, account-status, or playlist-modification requests.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-mwr9-5m78-rhgm
vulncheck.comvulncheck.com/advisories/avideo-cross-site-request-forgery-via-plugin-api-set-json-php

Frequently asked

questions

Yes. It can be triggered through a malicious URL or page, but successful

exploitation generally depends on a victim's authenticated browser session.

Usually not. The browser may automatically include the victim's existing

authentication cookies, provided the endpoint accepts the request and the

victim has the required permissions.

Restrict state-changing actions to appropriate non-GET methods and require

strong, session-bound CSRF tokens, with origin validation as an additional

control.

Apply CSRF protections consistently across authenticated APIs, prohibit

mutations through GET requests, review authorization boundaries, and test

endpoints with cross-origin request scenarios.

Find out what's already
exploitable in your codebase.