CVE-2026-11961
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 User Registration & Membership WordPress plugin before 5.2.3 does not validate that the membership tier submitted during public registration is one of the tiers allowed by the registration form before assigning that tier's associated user role, allowing unauthenticated users to register into an arbitrary published membership tier and obtain its role — up to administrator when such a tier exists.
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 User Registration & Membership WordPress plugin before 5.2.3 lacks server-side validation of the membership tier parameter during public registration. An unauthenticated attacker can submit an arbitrary published membership tier ID during registration, bypassing form-level restrictions, and automatically receive the role associated with that tier — including administrator privileges if such a tier exists.
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.
-
Confirm the plugin is installedNavigate to WordPress admin > Plugins and locate 'User Registration & Membership' or check the plugin directory for the membership filesAffected if The plugin is installed and active
-
Identify the installed plugin versionIn Plugins list, look for the version number under the plugin name, or check the plugin's main PHP file for the Version header commentAffected if Version is below 5.2.3 (e.g., 5.2.2, 5.2.1, etc.)
-
Verify public user registration is enabledGo to WordPress Settings > General > Membership: ensure 'Anyone can register' is checked, and check the User Registration plugin settings for active registration formsAffected if Public registration is enabled and at least one registration form is published
-
Inspect published membership tiers for elevated rolesIn User Registration plugin settings, view all membership tiers and check which published tiers are assigned to user roles; look for tiers granting Administrator, Editor, or other high-privilege rolesAffected if Any published membership tier is assigned a privileged role such as Administrator
You are affected if the plugin version is below 5.2.3, public user registration is enabled, and a published membership tier grants an elevated role that an attacker could inherit during registration.
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.
dbcve · scopedUpdate the plugin to version 5.2.3 or later, which implements server-side validation to ensure only membership tiers explicitly allowed by the registration form can be assigned during user registration.
Version 5.2.3 or later
- Upgrade the User Registration & Membership plugin to version 5.2.3 or later via the WordPress plugin administration panel, or manually download and install the updated plugin from the WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11961 — 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-11961 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