Members plugin vulnerability records and a read-only check of its roles and capabilities
Members writes role and capability changes straight into WordPress, and its documentation says they stay after the plugin is deactivated or deleted.
So a review reads the roles, what each is granted or denied, which posts carry Content Permissions, and who can open the Roles screens.
On this page
Members vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 2 records for Members. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 3.2.23
Worked out from data retrieved on .
Every affected range listed in this source for Members ends before version 3.2.23.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Members <= 3.2.22 - Unauthenticated Sensitive Information Disclosure via REST API Pagination Side Channel
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2026-12426
Affected versions- All versions up to and including 3.2.22
Patched versions: 3.2.23
Update to at least version 3.2.23.
Members <= 3.2.10 - Unauthenticated Content Restriction Bypass to Sensitive Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2024-11008
Affected versions- All versions up to and including 3.2.10
Patched versions: 3.2.11
Update to at least version 3.2.11.
Check Members on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What Members changes and who can reach its screens
The WordPress.org listing describes Members as a user interface for WordPress's own roles and capabilities system, and names features including a Role Editor, Multiple User Roles, Explicitly Deny Capabilities, role import and export, Content Permissions, Private Site and an AI Assistants (MCP) connection.
The vendor's Role Management page calls the changes made there permanent: the plugin is a user interface for changes made directly to the WordPress database, and deactivating or uninstalling it does not revert them. The vendor's docs overview says Members adds its own capabilities to the Administrator role so administrators can use the Members screens; the role editing check on this page names them.
Parts of Members face people who are not logged in. The listing's FAQ describes an Administrator Rescue form at wp-login.php?action=members_rescue that emails an eligible account a link restoring its Administrator role, and a members_login_form shortcode that puts a login form on any page.
What the Members record titles and version fields say
The records in the history on this page are the ones the source data files under the slug members.
CVE-2026-12426 has a title ending "Unauthenticated Sensitive Information Disclosure via REST API Pagination Side Channel"; its affected range is all versions up to and including 3.2.22, and its patched versions field lists 3.2.23. CVE-2024-11008 has a title ending "Unauthenticated Content Restriction Bypass to Sensitive Information Exposure", with all versions up to and including 3.2.10 in its affected range and 3.2.11 in its patched versions field.
Read those two ranges together: 3.2.11, the patched version of CVE-2024-11008, falls inside the affected range of CVE-2026-12426. So a site that stopped at 3.2.11 still matches a record: check the installed version against each affected range in the history on this page before reading the update guidance at the top of the history.
The changelog on the plugin's WordPress.org listing names CVE-2026-12426 in its 3.2.23 entry, and starts some entries with "Security:", among them changes to Private Site mode and to Content Permissions. Read those entries as well as the update guidance at the top of the history before updating.
Reading Members roles, capabilities and permissions without changing them
Each check reads a screen on a site you are authorised to review, and some Members screens save as soon as you act.
The Role Management page says changes reach the database the moment you click Update, and the Content Permissions page says the block editor's panel saves automatically. Tick nothing, and leave every Update button and the Reset to Default WordPress Roles button under Members > Settings alone: the Role Management page says Reset Roles also removes any custom roles created with Members.
The Description column on the Plugins screen includes the version number; record it with the date. On Members > Add-Ons, note which add-ons are on without touching the toggles. The add-ons page says capabilities an add-on gave to roles stay after it is turned off, until someone changes them.
The Roles screen under the Members menu lists every role with three numbers, Users, Granted and Denied, and the Role Management page says Granted and Denied count capabilities, not people. Record each role and its numbers, and mark any role beyond the WordPress defaults: Super Admin, Administrator, Editor, Author, Contributor and Subscriber.
The same page says a role showing "This role is not editable." is locked by another plugin or beyond what your own role may edit.
For who holds each role, use the Role column and the role filter links on the WordPress Users screen. The Settings page gives Multiple User Roles as on by default, and the Multiple User Roles page says the edit user screen then has a "Roles" section with a checkbox for every role. Read it and leave without clicking Update User.
Opening a role shows its "Edit Capabilities" box and a Filter capabilities search box; search by name and read each state. The docs overview says WordPress roles are not hierarchical, and that the Subscriber role could be given more capabilities than the Administrator role. Read every role's list rather than judging it by its name.
For each role other than Administrator, record the capabilities these pages describe. The Capabilities Guide says create_users and promote_users let someone assign any role, including Administrator. WordPress's Roles and Capabilities page lists capabilities that only Administrators hold on a single site, among them install_plugins, edit_plugins and edit_users.
Then note each role's Denied count, and whether "Denied capabilities should always overrule granted capabilities" is on under Members > Settings, which the Settings page gives as on by default.
On Members > Settings, record whether Enable Permissions and Hide Protected Posts from WP REST API are on (the Settings page gives both as on by default) and the Private Site settings. On each protected post or page, read the roles in the Content Permissions (Members) panel of the block editor's settings sidebar, or in the meta box below the classic editor.
The Content Permissions page says a child page with no roles ticked takes its parent's roles when the parent has some ticked.
Then open each protected address logged out, in a private window. The Content Permissions page says the feature does not hide the title, featured image, menus, search results, sitemaps, uploaded files, custom fields shown outside the post content, the Posts page, content from page builders that do not use the post content, or WooCommerce products beyond their description. Note what still shows, including any linked PDF.
The Capabilities Guide's table of who can use the Members screens names list_roles, create_roles, edit_roles, delete_roles, restrict_content and manage_options. List every role holding one of them, or create_users or promote_users, and the users in each. The add-ons page says that without the Role Hierarchy add-on, anyone who can edit users can give anyone any role, including Administrator; if the add-on is on, record its rule under Members > Settings > Roles and Capabilities.
On multisite, the listing's FAQ says only Super Admins can create, edit and delete roles by default, and that adding create_roles, edit_roles or delete_roles to a role on a sub-site allows it there. Read each sub-site's roles for those three.
Last, open Members > Settings > AI (MCP) and record whether Read-only mode is on, which groups are switched on under Advanced mode > Show actions, and what the Activity list shows. Do not click "Install & activate" or "Create password & fill it in".
The vendor's guide says the first installs the MCP Adapter plugin and the second creates an Application Password for the account you are logged in as, and that the password signs in for the whole REST API, not only Members.
What a Members version match leaves unread
A version match shows whether the site sits inside a known record.
It does not show whether anyone used the flaw, and it reads nothing Members has written into WordPress: the custom roles, what a cloned role was granted, who holds several roles, or who can open the Roles screens.
A WordPress security audit signs in as each role with test accounts, tries the actions that role should be refused and records what actually happened. Roles and capabilities that plugins add are where it spends most of its time.
Frequently asked questions
Not according to the vendor. Its Role Management page says roles and capabilities stay exactly as they are if Members is deactivated or deleted, because they live in WordPress itself. On a site that has removed it, the Role column and role filter links on the Users screen still show who holds each role.
The records are the ones the source data files under the slug members, and being filed there does not settle whether a record also applies to another product. The listing's FAQ describes MemberPress as a premium membership platform designed to work with Members, which it calls a free roles and capabilities plugin. The add-ons page says each add-on comes with Members and stays off until turned on under Members > Add-Ons.
The vendor's Connect AI Assistants guide says Members' tools start read-only, that allowing changes means turning off Read-only mode on the AI (MCP) tab, that the groups of actions that change things include Manage roles and Manage users' roles, and that the assistant acts as the WordPress account its password belongs to. Record the read-only state, the switched-on groups and that account.
The listing's FAQ says only users with the built-in WordPress Administrator role, or Super Admins on multisite, can use it, and that custom or cloned roles are not eligible. The link goes to the account's email address, so record whether each Administrator's address is one the business controls.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to every record listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.