/

CVE-2026-88872

Severity:

HIGH RISK

(7.1)

CSRF (CWE-352) in AVideo Channel Password Function

CVE-2026-88872

Deferred

Vulnerability type

Category:

Cross-Site Request Forgery

CWE:

CWE-352

Impact:

Unauthorized password modification and potential account takeover

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 setPassword.json.php endpoint. An attacker may use a crafted webpage to cause an authenticated administrator's browser to modify or clear another user's channel password because the request does not require a valid CSRF token.

Affected context

The vulnerability occurs in AVideo deployments where the setPassword.json.php endpoint accepts password-changing requests through GET requests without validating a CSRF token. Risk is present when an administrator is authenticated in the same browser and can be induced to visit attacker-controlled content.

Exploit preconditions

  • Attack surface: The AVideo setPassword.json.php web endpoint
  • Required access: No direct AVideo authentication is required for the attacker; an authenticated administrator must be available as the request origin
  • Trigger point: A victim administrator visits a malicious page or follows attacker-controlled content
  • Why exploitation is possible: The password-changing action accepts a browser-submitted request without sufficient CSRF validation, allowing ambient administrator credentials to be reused

Why this happens

The underlying issue is a state-changing operation that relies on the browser's authenticated session without requiring proof that the request originated from the AVideo application. This maps to CWE-352: Cross-Site Request Forgery, where an attacker can cause a victim's browser to submit an unintended action because request origin and intent are not adequately verified.

Potential impact

  • An attacker could modify or clear a user's channel password
  • Affected users may lose access to their channels
  • Attackers could gain access if a changed password is known or controlled by them
  • Administrative workflows and channel ownership could be disrupted
  • The vulnerability could contribute to unauthorized account access or data exposure

General mitigation guidance

Mitigation generally focuses on protecting every state-changing endpoint against cross-origin request forgery and reducing the authority of administrative actions.

Common defensive patterns include:

  • Requiring unpredictable, session-bound CSRF tokens for password and account changes
  • Rejecting state-changing requests that lack valid anti-CSRF credentials
  • Using appropriate same-site cookie settings as defense in depth
  • Restricting password-changing operations to methods intended for state changes rather than GET
  • Applying reauthentication or step-up verification for sensitive administrative actions
  • Enforcing least privilege for administrative roles and account-management functions
  • Avoiding reliance on origin or referrer checks as the sole protection

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag state-changing logic reachable through GET requests
  • Code review checks for missing CSRF-token generation and validation
  • Testing administrative endpoints from cross-origin pages while monitoring whether actions succeed
  • Web application policies requiring CSRF protection for password, role, and account-management operations
  • Runtime logging and alerting for unexpected password changes or unusual administrative activity
  • Automated security testing and neutral code-review tools that model authenticated cross-origin requests

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-h8vg-wg8w-4r6v
vulncheck.comvulncheck.com/advisories/avideo-customizeuser-setpassword-json-php-csrf

Frequently asked

questions

Yes, in the sense that an attacker can host or distribute a malicious webpage remotely. However, successful exploitation generally depends on an authenticated administrator visiting that content while an active AVideo session is available.

The described attack does not require the attacker to authenticate to AVideo. The important prerequisite is access to a way to deliver attacker-controlled content to an authenticated administrator.

Protect the password-changing endpoint with a strong, session-bound CSRF token, use a state-changing HTTP method, and consider reauthentication or additional confirmation for sensitive administrative actions.

Apply a consistent CSRF protection policy to all state-changing endpoints, prohibit security-sensitive changes through GET requests, use secure cookie attributes, and include cross-origin request testing in code review and security testing.

Find out what's already
exploitable in your codebase.