dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11963

HIGH · 8.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 6 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 User Registration & Membership WordPress plugin before 5.2.2 does not perform an authorization check on a membership-upgrade action and derives the user to modify from a caller-supplied identifier instead of the current user, allowing any authenticated user such as a subscriber to change another user's WordPress role and membership tier.

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 User Registration & Membership WordPress plugin before 5.2.2 lacks proper authorization validation on its membership-upgrade endpoint and uses a caller-supplied user identifier rather than deriving it from the authenticated session, enabling any authenticated user (including low-privilege subscribers) to modify another user's WordPress role and membership tier via IDOR.

MitigationUpdate the plugin to version 5.2.2 or later which implements proper authorization checks and uses the current user's ID instead of caller-supplied input.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Identify the plugin installation
    Check if the User Registration & Membership WordPress plugin is installed on the site by inspecting the wp-content/plugins directory or the WordPress plugin admin interface
    Affected if The plugin is installed and active
  2. Determine the installed plugin version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate the User Registration & Membership plugin to view its current version number
    Affected if The installed version is lower than 5.2.2 (for example 5.2.1, 5.2.0, or earlier)
  3. Verify membership-upgrade endpoint accessibility
    If you have access to the site's HTTP traffic or configuration, check if the membership-upgrade endpoint exists and is accessible to authenticated users. This may involve reviewing the plugin's registered REST API routes or AJAX handlers
    Affected if The membership-upgrade endpoint is exposed and accepts user-supplied identifiers
  4. Test authorization on the membership-upgrade endpoint
    Using a low-privilege account (such as a subscriber), attempt to access the membership-upgrade endpoint with a modified user_id parameter pointing to a different user account
    Affected if The request succeeds and allows modifying another user's role or membership tier without proper authorization

A user is affected if the User Registration & Membership plugin is installed with a version earlier than 5.2.2 and the membership-upgrade endpoint permits a low-privilege authenticated user to modify another user's role or membership tier via a caller-supplied identifier.

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 the plugin to version 5.2.2 or later which implements proper authorization checks and uses the current user's ID instead of caller-supplied input.

Recommended fix Moderate confidence

5.2.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'User Registration & Membership' plugin
  4. Check the current version installed
  5. If the installed version is before 5.2.2, click 'Update Now' to update to version 5.2.2 or latest available version
  6. Alternatively, download the latest version from wordpress.org/plugins/user-registration/ and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number reflects 5.2.2 or later
  8. Test that the membership upgrade functionality works correctly for the current user only (not other users)
Caveat Review plugin changelog for potential breaking changes between current and 5.2.2, particularly regarding membership tier functionality

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11963 — 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-11963 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