dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11965

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 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.0 does not enforce payment completion before activating a paid membership subscription, allowing unauthenticated users (after self-registering an account through the open registration flow) to obtain an active subscription on any paid plan without paying and access the gated content.

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 · moderate confidence

The User Registration & Membership WordPress plugin before 5.2.0 fails to validate payment completion before activating paid membership subscriptions. Unauthenticated users who self-register through the open registration flow can obtain active subscriptions on any paid plan without any payment transaction occurring, then access gated content intended only for paying members.

MitigationUpgrade to version 5.2.0 or later which implements proper payment validation before activating paid subscriptions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'User Registration & Membership' or check the plugin files in wp-content/plugins/ for a folder named similarly to 'user-registration-membership'
    Affected if The plugin is not installed - no action needed
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the 'User Registration & Membership' plugin, or read the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if Version is lower than 5.2.0 - the vulnerability is present
  3. Verify registration is enabled
    In WordPress admin, go to User Registration > Settings > General tab and check if the setting 'Enable User Registration' is turned on
    Affected if Registration is enabled - the vulnerable flow is active
  4. Confirm paid membership plans exist and are selectable at registration
    In WordPress admin, go to User Registration > Memberships > Membership Plans and verify there is at least one 'Paid' plan (not Free). Then go to User Registration > Settings > General and check if 'Select Membership Plan' is enabled in the registration form settings
    Affected if Paid membership plans exist and users can select a paid plan during self-registration - exploitation is possible

The environment is affected if the plugin is installed with a version below 5.2.0, user registration is enabled, and paid membership plans can be selected during the open registration flow.

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

Upgrade to version 5.2.0 or later which implements proper payment validation before activating paid subscriptions.

Recommended fix Moderate confidence

User Registration & Membership plugin version 5.2.0

  1. Upgrade the User Registration & Membership WordPress plugin to version 5.2.0 or later
  2. Verify the upgrade was successful by checking the plugins page in WordPress admin
  3. Test the registration flow to confirm payment is now enforced before subscription activation
  4. Ensure existing paid memberships are functioning correctly after the upgrade
  5. Review user access logs to confirm no unauthorized free access occurred prior to the patch

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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