CVE-2026-1321
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 · uneditedThe Membership Plugin – Restrict Content plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.2.20. This is due to the `rcp_setup_registration_init()` function accepting any membership level ID via the `rcp_level` POST parameter without validating that the level is active or that payment is required. Combined with the `add_user_role()` method which assigns the WordPress role configured on the membership level without status checks, this makes it possible for unauthenticated attackers to register with any membership level, including inactive levels that grant privileged WordPress roles such as Administrator, or paid levels that charge a sign-up fee. The vulnerability was partially patched in version 3.2.18.
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 confidenceThe Membership Plugin – Restrict Content for WordPress contains a privilege escalation vulnerability in versions up to 3.2.20. The `rcp_setup_registration_init()` function accepts any membership level ID via the `rcp_level` POST parameter without validating that the level is active or that payment is required. Combined with the `add_user_role()` method that assigns WordPress roles without status checks, unauthenticated attackers can register with any membership level—including inactive ones that grant Administrator roles—or bypass payment on paid levels.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Membership Plugin - Restrict Content' (or 'Restrict Content Pro'). The version number is displayed below the plugin name. Alternatively, check the main plugin file header for the 'Version' tag.Affected if The installed version is 3.2.20 or lower.
-
Confirm user registration is enabledNavigate to WordPress Settings > General and verify that the 'Membership' checkbox is checked (labeled 'Anyone can register'). This setting must be enabled for the vulnerable registration function to be accessible.Affected if User registration is enabled on the WordPress site.
-
Review membership levels and assigned rolesIn the WordPress admin, go to Restrict Content > Membership Levels. Examine each level and note the assigned WordPress role in the 'Role' dropdown. Pay particular attention to levels with Administrator or Editor roles.Affected if Any membership level (active or inactive) is assigned an elevated role such as Administrator.
-
Check for inactive membership levelsIn Restrict Content > Membership Levels, identify any levels marked as 'Inactive' or with a status other than 'Active'. These can be exploited per the vulnerability description.Affected if There exists at least one inactive membership level, regardless of its assigned role.
-
Verify payment requirement status on paid levelsIn Restrict Content > Membership Levels, examine paid levels and check if they have a price set. The vulnerability allows bypassing payment, so any paid level could be exploited.Affected if Any paid membership level exists on the site.
If the plugin version is 3.2.20 or lower AND user registration is enabled AND any membership level has an elevated role OR there are inactive levels, the site is likely vulnerable to privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to the latest version of the plugin and ensure proper validation is in place for membership level activation status and payment verification before role assignment.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1321 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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