Ultimate Member <= 2.0.6 - Multiple Cross-Site Request Forgery Issues
Strategic Overview
- Status
- Patched in 2.0.7
- Affected Plugin
- Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
- Affected Version
< 2.0.7- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2018-10233
At a glance
CVE-2018-10233 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Ultimate Member WordPress plugin, affecting versions < 2.0.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.7; sites on affected versions should update now. Disclosed April 2018, reported by Riccardo ten Cate.
Vulnerability Overview
The User Profile & Membership plugin before 2.0.7 for WordPress has no mitigations implemented against cross site request forgery attacks. This is a structural finding throughout the entire plugin.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Ultimate Member < 2.0.7 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Ultimate Member the fix is 2.0.7: builds < 2.0.7 are affected, anything from 2.0.7 onward is not.
Remediation
Update to version 2.0.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Ultimate Member: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ultimate Member 2.0.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
- 10.0CVE-2020-36157: Ultimate Member <= 2.1.11 Privilege Escalation
CVE-2020-36157 - 10.0CVE-2020-36155: Ultimate Member <= 2.1.11 Privilege Escalation
CVE-2020-36155 - 9.9CVE-2020-36156: Ultimate Member <= 2.1.11 Privilege Escalation
CVE-2020-36156 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C