Ultimate Member <= 2.11.0 - Authenticated (Subscriber+) Profile Privacy Setting Bypass
Strategic Overview
- Status
- Patched in 2.11.1
- Affected Plugin
- Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
- Affected Version
<= 2.11.0- CVSS
- 4.3Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2025-14081
At a glance
CVE-2025-14081 is a medium-severity Incorrect Authorization vulnerability in the Ultimate Member WordPress plugin, affecting versions <= 2.11.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.11.1; sites on affected versions should update now. Disclosed December 2025, reported by Boris Bogosavac.
Vulnerability Overview
The Ultimate Member plugin for WordPress is vulnerable to Profile Privacy Setting Bypass in all versions up to, and including, 2.11.0. This is due to a flaw in the secure fields mechanism where field keys are stored in the allowed fields list before the `required_perm` check is applied during rendering. This makes it possible for authenticated attackers with Subscriber-level access to modify their profile privacy settings (e.g., setting profile to "Only me") via direct parameter manipulation, even when the administrator has explicitly disabled the option for their 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.
CWE-863: Incorrect Authorization
Reaching this weakness in Ultimate Member <= 2.11.0 takes an account at Subscriber level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Ultimate Member the fix is 2.11.1: builds <= 2.11.0 are affected, anything from 2.11.1 onward is not.
Remediation
Update to version 2.11.1, 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: Ultimate Member 2.11.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
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