The MDJM Event Management plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.7.8.4. This is due to missing capability checks and nonce verification in the `MDJM_Permissions::set_permissions()` and `MDJM_Employee_Manager::init()` functions, combined with the absence of server-side allow-list validation on the `employee_roles[]` and `new_role` POST parameters before they are passed to `mdjm_set_employee_role()` and `WP_User::set_role()`. This makes i
The MDJM Event Management plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.7.8.4. This is due to missing capability checks and nonce verification in the MDJM_Permissions::set_permissions() and MDJM_Employee_Manager::init() functions, combined with the absence of server-side allow-list validation on the employee_roles[] and new_role POST parameters before they are passed to mdjm_set_employee_role() and WP_User::set_role(). This makes it possible for unauthenticated attackers to grant arbitrary MDJM capabilities — including mdjm_employee and mdjm_employee_edit — to any registered WordPress role, and subsequently leverage a subscriber-level account to escalate privileges to Administrator. MDJM_Permissions::init() is registered on the public WordPress init hook without any authentication gate, meaning the role-manipulation endpoint is reachable without any prior login.
Why this VPI (explainable, experimental)
VPI breakdown
| Impact | 88.00 |
| Exploitation signal(No additional exploitation signal) | ×1.00 |
| VPI | 88.00 |
VPI formula vpi-v1