Summary
The endpoint plugin/Permissions/View/Users_groups_permissions/list.json.php lacks any authentication or authorization check, allowing unauthenticated users to retrieve the complete permission matrix mapping user groups to plugins. All sibling endpoints in the same directory (add.json.php, delete.json.php, index.php) properly require User::isAdmin(), indicating this is an oversight.
Details
The vulnerable file at plugin/Permissions/View/Users_groups_permissions/list.json.php:1-7 contains:
<?php
require_once '../../../../videos/configuration.php';
require_once $global['systemRootPath'] . 'plugin/Permissions/Objects/Users_groups_permissions.php';
header('Content-Type: application/json');
$rows = Users_groups_permissions::getAll();
?>
{"data": <?php echo json_encode($rows); ?>}
This calls ObjectYPT::getAll() (defined in objects/Object.php:98-111), which executes:
$sql = "SELECT * FROM " . static::getTableName() . " WHERE 1=1 ";
$sql .= self::getSqlFromPost();
This returns all rows from the users_groups_permissions table as JSON with no access control.
Compare with the sibling add.json.php:10-15 and delete.json.php:9-14, which both enforce:
$plugin = AVideoPlugin::loadPluginIfEnabled('Permissions');
if(!User::isAdmin()){
$obj->msg = "You cant do this";
die(json_encode($obj));
}
Similarly, index.php:6-8 (the admin page that loads this data via AJAX) checks:
if (!User::isAdmin()) {
forbiddenPage("You can not do this");
exit;
}
No .htaccess or web server configuration restricts direct access to this endpoint.
PoC
# Retrieve complete permission mappings without authentication
curl -s https://target/plugin/Permissions/View/Users_groups_permissions/list.json.php
Expected response (admin-only data):
{"data": [{"id":"1","name":null,"users_groups_id":"2","plugins_id":"5","type":"1","status":"a"}, ...]}
Each row reveals:
users_groups_id, numeric ID of a user groupplugins_id, numeric ID of an installed plugintype, the permission level grantedstatus, whether the permission is active (a) or inactive
The getSqlFromPost() method also processes $_POST['sort'] and $_GET parameters, allowing an attacker to paginate and sort results to extract all data systematically.
Impact
An unauthenticated attacker can enumerate the complete authorization model of the AVideo instance:
- All user group IDs and which plugins each group can access
- All installed plugin IDs and their permission configurations
- Permission types and active/inactive status for each group-plugin pair
This information provides a detailed roadmap of the application's authorization architecture, significantly aiding targeted privilege escalation, as an attacker would know exactly which groups have access to which plugins and what permission types are assigned. While not directly exploitable for data modification, it reduces the attacker's effort for follow-up attacks.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
CVE-2026-33501 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Add the same admin authorization check used by the sibling endpoints. In plugin/Permissions/View/Users_groups_permissions/list.json.php:
<?php
require_once '../../../../videos/configuration.php';
require_once $global['systemRootPath'] . 'plugin/Permissions/Objects/Users_groups_permissions.php';
header('Content-Type: application/json');
$plugin = AVideoPlugin::loadPluginIfEnabled('Permissions');
if(!User::isAdmin()){
die(json_encode(['error' => true, 'msg' => 'You cant do this']));
}
$rows = Users_groups_permissions::getAll();
?>
{"data": <?php echo json_encode($rows); ?>}
Frequently Asked Questions
- What is CVE-2026-33501? CVE-2026-33501 is a medium-severity missing authorization vulnerability in wwbn/avideo (composer), affecting versions <= 26.0. No fixed version is listed yet. The application does not perform an authorization check before performing a sensitive operation.
- How severe is CVE-2026-33501? CVE-2026-33501 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of wwbn/avideo are affected by CVE-2026-33501? wwbn/avideo (composer) versions <= 26.0 is affected.
- Is there a fix for CVE-2026-33501? No fixed version is listed for CVE-2026-33501 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2026-33501 exploitable, and should I be worried? Whether CVE-2026-33501 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-33501 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-33501? No fixed version is listed yet. In the interim: Keep the dependency up to date. Ensure authorization checks are enforced consistently on all sensitive operations.