CVE-2025-14081 MEDIUM

CVE-2025-14081: Ultimate Member <= 2.11.0 - Authenticated (Subscriber+) Profile Privacy Setting Bypass

Vendor Ultimatemember
Product Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
Weakness CWE-863 · Incorrect authorization
Published December 17, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Ultimate Member plugin versions up to 2.11.0 contain an authorization flaw that allows authenticated users to modify content they should not have access to. The vulnerability requires a logged-in account but no special privileges. An attacker with a standard user account can alter data through the plugin's functionality, potentially affecting site integrity.

What an attacker can do

03Attacker Capabilities

Modify content or data they should not have permission to change.

Potential impact on your site

04Site Impact

Any registered user can alter site data or other users' content, compromising data integrity and trust.

Conditions required to exploit

05Prerequisites

Attacker must have a valid user account and be logged in to the site.

Key dates

06Disclosure timeline

December 17, 2025 CVE published
April 8, 2026 Record updated