# CVE-2026-4136: Membership Plugin – Restrict Content <= 3.2.24 - Unvalidated Redirect in Password Reset Flow via rcp_redirect

> Unauthenticated attackers can redirect users to malicious sites via the password reset flow in the Restrict Content plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-434r-hj47-rpjj

## What is CVE-2026-4136?

CVE-2026-4136 is a medium-severity vulnerability in stellarwp Membership Plugin – Restrict Content, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2026-4136?


## How do I fix CVE-2026-4136?

No fix has been published for CVE-2026-4136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4136 being exploited?

There is no known exploitation of CVE-2026-4136 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4136 and fix it if it is affected.

What it is: CVE-2026-4136 is a medium-severity vulnerability in stellarwp Membership Plugin – Restrict Content, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-4136 in the wild and no public exploit code.

Affected product: stellarwp Membership Plugin – Restrict Content. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4136/ (Markdown: https://insights.sbomify.com/CVE-2026-4136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4136
- OSV: https://osv.dev/vulnerability/CVE-2026-4136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4136/
Summaries are generated and may contain mistakes; the official description above is the record.