/

CVE-2026-33649

Severity:

HIGH RISK

(8.1)

Cross-Site Request Forgery (CSRF) in WWBN AVideo

CVE-2026-33649

Analyzed

Vulnerability type

Category:

Cross-Site Request Forgery (CSRF)

CWE:

CWE-352

Impact:

Privilege Escalation via Cross-Site Request Forgery

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

WWBN AVideo exposes a state-changing permission management endpoint that can be triggered via cross-site requests without CSRF protection.

If an administrator visits a malicious page while logged in, an attacker can silently modify user group permissions and escalate their own account to near-admin privileges.

Affected context

The vulnerability occurs in WWBN AVideo deployments (up to and including version 26.0) where the plugin/Permissions/setPermission.json.php endpoint is reachable by authenticated administrators.

The endpoint performs state-changing operations based solely on GET parameters, without CSRF token validation, while the application explicitly configures session.cookie_samesite=None.

In environments where administrators browse the internet while authenticated to the AVideo instance, visiting attacker-controlled web pages can trigger unintended permission changes.

Exploit preconditions

  • Attack surface: Web-based, via the plugin/Permissions/setPermission.json.php HTTP endpoint.
  • Required access: The attacker needs either:
  • Any valid user-group account whose permissions they wish to escalate, or
  • Knowledge of target group identifiers used by the application.
  • Victim role: An authenticated administrator (or privileged user) who has permission to modify user group permissions.
  • User interaction: The victim must visit or be embedded into an attacker-controlled page (e.g., through a link, iframe, or injected content) while logged in to the AVideo admin interface.
  • Trigger point: The victim's browser automatically loads crafted <img> or similar tags that issue GET requests to setPermission.json.php with attacker-controlled parameters.
  • Why exploitation is possible: The endpoint:
  • Accepts state-changing requests via GET.
  • Does not validate CSRF tokens or enforce an origin/referrer policy.
  • Uses session cookies with SameSite=None, allowing them to be sent on cross-site requests.

Why this happens

This issue stems from missing cross-site request forgery defenses on a sensitive, state-changing endpoint that modifies permission settings.

The plugin/Permissions/setPermission.json.php endpoint performs authorization-significant actions based purely on session cookies and attacker-controlled GET parameters, without requiring a CSRF token or validating the request origin.

Combined with an explicit session.cookie_samesite=None configuration, the browser includes authentication cookies on cross-site requests, enabling external websites to trigger privileged actions.

This aligns with CWE-352: Cross-Site Request Forgery (CSRF), where a web application fails to distinguish between legitimate user-driven requests and attacker-initiated cross-origin requests for critical operations.

Potential impact

  • Attacker-controlled user group may gain near-admin or highly privileged permissions.
  • Unauthorized changes to role- or group-based access controls across the platform.
  • Escalation from low-privilege user to a position capable of managing videos, users, or settings, depending on granted rights.
  • Indirect compromise of content integrity, user privacy, or configuration via abused elevated permissions.
  • Facilitation of further attacks, such as content defacement, data exfiltration, or account takeovers managed via administrative interfaces.

General mitigation guidance

Effective mitigation typically focuses on strengthening request authenticity checks and reducing the risk of cross-origin side effects on sensitive endpoints:

  • Require robust CSRF tokens for all state-changing operations, validating them server-side for both POST and any non-idempotent methods.
  • Avoid using GET for state-changing endpoints; favor POST (or other non-idempotent verbs) and enforce content-type checks to distinguish browser-initiated form submissions from background resource loads.
  • Reconsider SameSite cookie configuration; where feasible, prefer Lax or Strict for session cookies associated with administrative interfaces, balancing usability and security.
  • Introduce server-side checks on Origin and/or Referer headers for administrative actions, rejecting requests not originating from trusted domains.
  • Segment administrative and public functionality, including separate subdomains or paths with stricter CSRF and cookie policies for admin areas.
  • Apply principle of least privilege to group permissions so that the impact of any unintended change is minimized.

How teams detect issues like this

Detection can target both insecure patterns in code and unusual behavior at runtime:

  • Static analysis and code review:
  • Flag state-changing endpoints that:
  • Accept GET requests for operations that modify permissions, roles, or configuration.
  • Lack CSRF token validation or origin/referrer checks.
  • Identify explicit configuration of session.cookie_samesite=None for session cookies tied to admin functions, and verify compensating CSRF controls.
  • Review permission management code paths for absence of anti-CSRF mechanisms.
  • Runtime and log-based monitoring:
  • Monitor access logs for permission changes resulting from GET requests or from unusual referrers/origins.
  • Alert on bursts of permission modifications tied to a single administrator session or IP in a short time window.
  • Security testing:
  • Include CSRF tests in regular application security assessments, using automated scanners and manual test cases around administrative and permission management endpoints.
  • Integrate automated review tools into CI pipelines to enforce policies that disallow state changes without CSRF protection.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-g8x9-7mgh-7cvj

Frequently asked

questions

Yes. An attacker can host a malicious web page and trick an authenticated administrator into visiting it. When the page loads, the victim's browser can issue cross-site requests to the vulnerable AVideo instance, leveraging the admin's session cookies to change permissions.

The attacker does not need administrative access but typically benefits from having, or targeting, a specific user group that can be escalated. The critical precondition is that a privileged user is authenticated in the browser and visits attacker-controlled content.

Require CSRF tokens on all permission-changing and administrative endpoints, avoid using GET for state-changing operations, and ensure that session cookies for admin functions use conservative SameSite settings or are protected by strong CSRF and origin checks.

Establish a standard security pattern for all state-changing routes: enforce CSRF protection, restrict methods to POST/PUT/DELETE, validate origins, and perform regular security reviews focusing on administrative and permission-related endpoints. Incorporating these patterns into development frameworks and CI checks helps prevent regressions.

Find out what's already
exploitable in your codebase.