Premmerce User Roles <= 1.0.12 - Missing Authorization via role management functions
Strategic Overview
- Status
- Patched in 1.0.13
- Affected Plugin
- Premmerce User Roles
- Affected Version
<= 1.0.12- CVSS
- 8.3High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-41130
At a glance
CVE-2023-41130 is a high-severity Missing Authorization vulnerability in the Premmerce User Roles WordPress plugin, affecting versions <= 1.0.12. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity; high confidentiality, integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.0.13; sites on affected versions should update now. Disclosed August 2023, reported by Nguyen Xuan Chien.
Vulnerability Overview
The Premmerce User Roles plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to missing capability and nonce checks on the 'createRole', 'updateRole', and 'deleteRole' functions in versions up to, and including, 1.0.12. This makes it possible for authenticated attackers, with subscriber-level access and above, to create, modify, and delete custom roles.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.
CWE-862: Missing Authorization
Premmerce User Roles <= 1.0.12 carries this weakness at createRole, and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Premmerce User Roles the fix is 1.0.13: builds <= 1.0.12 are affected, anything from 1.0.13 onward is not.
Remediation
Update to version 1.0.13, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Premmerce User Roles 1.0.13 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C