Ultimate Member <= 2.1.11 - Unauthenticated Privilege Escalation via User Meta
Strategic Overview
- Status
- Patched in 2.1.12
- Affected Plugin
- Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
- Affected Version
< 2.1.12- CVSS
- 10.0Critical
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2020-36155
At a glance
CVE-2020-36155 is a critical-severity Improper Privilege Management vulnerability in the Ultimate Member WordPress plugin, affecting versions < 2.1.12. It carries a CVSS score of 10.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.1.12; sites on affected versions should update now. Disclosed November 2020, reported by Chloe Chamberland.
Vulnerability Overview
An issue was discovered in the Ultimate Member plugin before 2.1.12 for WordPress, aka Unauthenticated Privilege Escalation via User Meta. An attacker could supply an array parameter for sensitive metadata, such as the wp_capabilities user meta that defines a user's role. During the registration process, submitted registration details were passed to the update_profile function, and any metadata was accepted, e.g., wp_capabilities[administrator] for Administrator access.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
Reaching this weakness in Ultimate Member < 2.1.12 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Ultimate Member the fix is 2.1.12: builds < 2.1.12 are affected, anything from 2.1.12 onward is not.
Remediation
Update to version 2.1.12, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Ultimate Member 2.1.12 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 10.0CVE-2020-36157: Ultimate Member <= 2.1.11 Privilege Escalation
CVE-2020-36157 - 9.9CVE-2020-36156: Ultimate Member <= 2.1.11 Privilege Escalation
CVE-2020-36156 - 8.8CVE-2019-10270: Ultimate Member <= 2.0.39 Privilege Escalation
CVE-2019-10270 - 7.3CVE-2026-19423: Ultimate Member Privilege Escalation
CVE-2026-19423
Other vulnerabilities in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
- 9.8CVE-2024-1071: Ultimate Member SQL Injection
CVE-2024-1071 - 9.8CVE-2023-3460: Ultimate Member <= 2.6.6 Privilege Escalation
CVE-2023-3460 - 9.8Ultimate Member <= 1.3.83 Shortcode Injection
- 9.8Ultimate Member <= 1.3.75 Password Reset
- 9.8Ultimate Member Authorization Bypass to Arbitrary File Upload/Delete
- 9.4Ultimate Member Arbitrary File Deletion/Read
- 9.1Ultimate Member <= 1.3.64 Local File Inclusion
- 8.8CVE-2026-7761: Ultimate Member <= 2.11.4 Account Takeover
CVE-2026-7761
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C