dbcve.org
CWE-640Weakness · CWE-640

CVE-2026-9273

CRITICAL · 9.3 CVSS v3.1 Published 2026-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 2 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Membership Plugin – Kadence Memberships plugin for WordPress (formerly Restrict Content) is vulnerable to password reset link poisoning leading to account takeover in all versions up to, and including, 4.0.0. This is due to the legacy lost-password handler rc_process_lost_password_form() consuming the attacker-controlled rc_redirect POST parameter into two unvalidated sinks in legacy/includes/forms.php: wp_redirect( esc_url( $_POST['rc_redirect'] ) . ... ) at line 243, and add_query_arg( array( 'key' => $key, 'login' => ... ), $_POST['rc_redirect'] ) inside rc_send_password_reset_email() at line 306. The nonce required to reach the handler is broadcast by the public [login_form] shortcode at line 207 to any anonymous visitor. This makes it possible for unauthenticated attackers to issue a password-reset request for any account (including administrators) whose reset email body points the victim at an attacker-controlled host carrying a valid reset key/login. When the victim clicks the link, the reset key leaks to the attacker, who can replay it against the legitimate site to complete account takeover.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Kadence Memberships plugin (formerly Restrict Content) contains a password reset link poisoning vulnerability in its legacy lost-password handler rc_process_lost_password_form(). Attackers exploit an unvalidated rc_redirect POST parameter that gets used in both wp_redirect() and add_query_arg() when constructing password reset URLs. Since the required nonce is publicly exposed via the [login_form] shortcode, unauthenticated attackers can trigger password resets for any user and redirect the reset link to an attacker-controlled domain, capturing the reset key and enabling full account takeover.

MitigationUpdate to version 4.0.1 or later immediately. If an update is unavailable, disable the plugin and consider resetting passwords for all administrator accounts as a precaution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Kadence Memberships or Restrict Content plugin is installed
    In WordPress admin, go to Plugins and verify that 'Kadence Memberships' or the legacy 'Restrict Content' plugin is installed and active. Alternatively, check the wp-content/plugins/ directory for the restrict-content or kadence-memberships folder.
    Affected if Plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view details and locate the version number. Alternatively, open the main plugin PHP file (e.g., restrict-content.php or class-kadence-memberships.php) and look for the 'Version:' header comment.
    Affected if Version is earlier than 4.0.1 (versions prior to 4.0.1 are vulnerable)
  3. Identify if the [login_form] shortcode is in use
    Search your WordPress content (pages, posts, widgets, theme files) for the [login_form] shortcode. This shortcode exposes the nonce required by the vulnerable rc_process_lost_password_form() function.
    Affected if The [login_form] shortcode is present on any publicly accessible page
  4. Verify the legacy lost password handler is accessible
    Submit a POST request to the login page endpoint (typically /login/) including the rc_redirect parameter with an external URL. If the password reset email or redirect logic uses this uncontrolled parameter, the vulnerability is present.
    Affected if The rc_redirect parameter is accepted and used in password reset URL construction

You are affected if the Kadence Memberships/Restrict Content plugin is installed with a version below 4.0.1 AND the [login_form] shortcode is exposed on a public page, allowing unauthenticated attackers to poison password reset links.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 4.0.1 or later immediately. If an update is unavailable, disable the plugin and consider resetting passwords for all administrator accounts as a precaution.

Recommended fix Moderate confidence

Version 4.0.1 or later (any version > 4.0.0)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Kadence Memberships' (formerly Restrict Content)
  4. If an update is available, click 'Update Now'
  5. Alternatively, manually download the latest version from wordpress.org/plugins/kadence-memberships/
  6. Verify the updated version is greater than 4.0.0
  7. Confirm the plugin is active after update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9273 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data