User Role Editor <= 4.24 - Authenticated Privilege Escalation
Strategic Overview
- Status
- Patched in 4.25
- Affected Plugin
- User Role Editor
- Affected Version
< 4.25- CVSS
- 8.8High
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Authorization vulnerability in the User Role Editor WordPress plugin, affecting versions < 4.25. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 4.25; sites on affected versions should update now. Disclosed April 2016.
Vulnerability Overview
The User Role Editor plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the 'update' function in versions up to, and including, 4.24. This makes it possible for any authenticated attackers to grant themselves the administrator role.
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, availability — full site compromise territory.
CWE-285: Improper Authorization
User Role Editor < 4.25 carries this weakness at update, and reaching it takes any authenticated account. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For User Role Editor the fix is 4.25: builds < 4.25 are affected, anything from 4.25 onward is not.
Remediation
Update to version 4.25, 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: User Role Editor 4.25 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in User Role Editor
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C