CVE-2026-86406

User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder 4.4.6 - 5.2.7 - Authenticated (Subscriber+) Privilege Escalation

2026-09-14 00:00
Karthik Ramakrishnan

At a glance

CVE-2026-86406 is a medium-severity Improper Privilege Management vulnerability in the User Registration & Membership WordPress plugin, affecting versions 4.4.6 – 5.2.7. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.2.8; sites on affected versions should update now. Disclosed September 2026, reported by Karthik Ramakrishnan.

Vulnerability Overview

The User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder plugin for WordPress is vulnerable to Privilege Escalation in versions 4.4.6 through 5.2.7. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges beyond those intended 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-269: Improper Privilege Management

Reaching this weakness in User Registration & Membership 4.4.6 – 5.2.7 takes an account at Subscriber level or above. 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 User Registration & Membership the fix is 5.2.8: builds 4.4.6 – 5.2.7 are affected, anything from 5.2.8 onward is not.

Remediation

Update to version 5.2.8, 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 Registration & Membership 5.2.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C