AVideo's GET-Based CSRF in setPermission.json.php Enables Privilege Escalation via Arbitrary Permission Modification

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-33649: 0.18% estimated exploitation activity in the next 30 days; percentile 7.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The plugin/Permissions/setPermission.json.php endpoint accepts GET parameters for a state-changing operation that modifies user group permissions. The endpoint has no CSRF token validation, and the application explicitly sets session.cookiesamesite=None on session cookies. This allows an unauthenticated attacker to craft a page with <img tags that, when visited by an admin, silently grant arbitrary permissions to the attacker's user group — escalating the attacker to near-admin access. Details The root cause is a combination of three issues: 1. $REQUEST used instead of $POST (accepts GET parameters): plugin/Permissions/setPermission.json.php:14-24: The only authorization check is User::isAdmin() at line 10 — there is no CSRF token validation via isGlobalTokenValid(). 2. Session cookies set to SameSite=None: objects/includeconfig.php:134-141: This means the admin's session cookie is sent on cross-origin requests, including those initiated by <img src="..." tags on…

Published by the source

25 Mar 2026, 17:48 UTC

Last modified by the source

25 Mar 2026, 17:48 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g8x9-7mgh-7cvj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33649

Advisory: AVideo's GET-Based CSRF in setPermission.json.php Enables Privilege Escalation via Arbitrary Permission Modification
IDs: CVE-2026-33649, GHSA-g8x9-7mgh-7cvj
Record: https://patchnext.com/advisories/cve-2026-33649 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist wwbn/avideo: affected <= 26.0

## Suggested inspection (read-only)
- Packagist wwbn/avideo: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wwbn/avideo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g8x9-7mgh-7cvj (GitHub-reviewed advisory GHSA-g8x9-7mgh-7cvj lists affected ranges: Packagist wwbn/avideo >=0 <=26.0)

Commands are suggestions: review each one before running it.