CVE-2026-4136

Membership Plugin – Restrict Content <= 3.2.24 - Unvalidated Redirect in Password Reset Flow via rcp_redirect

2026-03-19 14:37
Supakiad S. (m3ez) (m3ez)

Strategic Overview

Status
Patched in 3.2.25
Affected Plugin
Membership Plugin – Kadence Memberships
Affected Version
<= 3.2.24
CVSS
4.3Medium
Weakness type
CWE-640 · Weak Password Recovery Mechanism for Forgotten Password
CVE
CVE-2026-4136
View all Membership Plugin – Kadence Memberships vulnerabilities

At a glance

CVE-2026-4136 is a medium-severity Weak Password Recovery Mechanism for Forgotten Password vulnerability in the Membership Plugin WordPress plugin, affecting versions <= 3.2.24. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.25; sites on affected versions should update now. Disclosed March 2026, reported by Supakiad S. (m3ez) (m3ez).

Vulnerability Overview

The Membership Plugin – Restrict Content plugin for WordPress is vulnerable to Unvalidated Redirect in all versions up to, and including, 3.2.24. This is due to insufficient validation on the redirect url supplied via the 'rcp_redirect' parameter. This makes it possible for unauthenticated attackers to redirect users with the password reset email to potentially malicious sites if they can successfully trick them into performing an action.

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 privileges on the target site.

CWE-640: Weak Password Recovery Mechanism for Forgotten Password

Membership Plugin <= 3.2.24 carries this weakness at rcp_redirect, and reaching it takes a caller who can reach the endpoint. A weak password recovery mechanism means the path that lets someone back into an account without their password is easier to complete than the password itself.

An attacker takes over an account through the recovery flow without ever seeing the password, and on an administrator account that is full control of the site. For Membership Plugin the fix is 3.2.25: builds <= 3.2.24 are affected, anything from 3.2.25 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-4136https://www.wordfence.com/threat-intel/vulnerabilities/id/e4cf42d3-9864-440b-8357-36c82cbef28fhttps://nvd.nist.gov/vuln/detail/CVE-2026-4136

Related records

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