CVE-2026-134751 in Members Plugininfo

Summary

by MITRE • 11/22/2026

Members WordPress plugin before 3.3.1 contains a missing authorization vulnerability that allows unauthenticated visitors to read role-restricted posts by viewing Latest Posts blocks in full-content mode. The block renders raw post_content without firing the_content filter, bypassing members_content_permissions_protect() and exposing complete bodies of restricted posts.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/22/2026

The Members WordPress plugin is a widely utilized tool for managing user roles and permissions within the WordPress ecosystem, providing granular control over content visibility based on user capabilities. A critical security flaw identified in versions prior to 3.3.1 involves a missing authorization check that fundamentally undermines these access controls. This vulnerability specifically affects the Latest Posts block when it is configured to display post content in full-content mode rather than as an excerpt or summary. The core technical issue stems from how the plugin renders this specific block type, where it directly outputs the raw database value of the post_content field without invoking standard WordPress filtering mechanisms that are designed to enforce permission checks.

In a typical WordPress environment, access restrictions for private or role-restricted posts are enforced through the application of filters such as the_content filter during the rendering process. This filter chain includes functions like members_content_permissions_protect(), which is responsible for verifying whether the current user has the necessary permissions to view specific content and subsequently masking or removing restricted text if those permissions are absent. However, in this vulnerable implementation, the Latest Posts block bypasses this critical security layer by outputting the raw post data directly. This architectural oversight means that the permission verification logic is never executed for these specific blocks, effectively creating a backdoor through which sensitive information can be accessed without authentication or proper authorization.

The operational impact of this vulnerability is significant because it allows unauthenticated visitors to read content that should be restricted to logged-in users with specific roles. An attacker does not need valid credentials or any form of interaction beyond simply visiting the webpage where these blocks are displayed. By viewing the page source or inspecting the rendered HTML, an external observer can retrieve the complete body text of posts marked as private, protected by password, or limited to certain user capabilities such as editors or administrators. This constitutes a severe breach of confidentiality and data integrity, potentially exposing proprietary information, internal communications, or personal data that was intended to remain hidden from the general public.

From a classification perspective, this vulnerability aligns with CWE-284, which describes Improper Access Control, specifically highlighting failures in enforcing restrictions on what authenticated users are allowed to do. It also relates closely to CWE-601, URL Redirection to Untrusted Site, if the block is used in conjunction with other elements that might leak context, but primarily it represents a failure in server-side access control logic. In terms of the MITRE ATT&CK framework for enterprise security, this behavior facilitates Information Discovery and potentially Data Exfiltration through publicly accessible web pages, allowing adversaries to gather intelligence without triggering typical intrusion detection systems associated with brute-force or injection attacks.

To mitigate this vulnerability, site administrators must immediately update the Members plugin to version 3.3.1 or later, where the rendering logic has been corrected to ensure that all content output respects existing permission filters and does not bypass standard security checks. Until an upgrade is performed, a temporary workaround involves disabling the Latest Posts block in full-content mode on public-facing pages or restricting access to those specific pages entirely through web server configuration rules such as .htaccess directives if feasible. Regular auditing of third-party plugins for similar patterns where raw database content is output without filtering is also recommended to prevent analogous vulnerabilities from being exploited elsewhere within the application environment.

Responsible

VulnCheck

Reservation

11/22/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!