CVE-2026-11964
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.2 does not verify the authenticity of incoming payment-provider webhook notifications before acting on them, allowing unauthenticated attackers to forge a payment-approved event and activate a paid membership subscription without completing a real payment.
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.2 lacks validation of incoming payment-provider webhook notifications, allowing unauthenticated attackers to forge payment-approved events and obtain paid membership subscriptions without making actual payments.
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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck your WordPress installation for the 'user-registration' plugin directory in wp-content/plugins/ or list installed plugins via WP admin panelAffected if The plugin directory exists and the plugin is active in WordPress
-
Check the plugin versionOpen wp-content/plugins/user-registration/user-registration.php and locate the 'Version:' header comment, or check the plugin row in WordPress plugins listAffected if The version number is lower than 5.2.2 (e.g., 5.2.1, 5.2.0, 5.1.x, etc.)
-
Confirm payment/membership module is activeIn WordPress admin, go to User Registration > Settings > General and verify that 'Enable Membership' or payment-related settings are turned on, or check for active payment addons in the plugins listAffected if Membership or payment processing features are enabled and configured
-
Inspect webhook handler accessibilityCheck if the webhook endpoint (typically /?user_registration_webhook=1 or similar in your site logs/htaccess) is publicly accessible without authenticationAffected if Webhook endpoints are reachable without authentication and process payment events
You are affected if the User Registration & Membership plugin is active with a version before 5.2.2 and payment/membership features are enabled, allowing unauthenticated webhook requests to be processed without signature validation.
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 · scopedUpgrade to version 5.2.2 or later which implements proper webhook signature verification before processing payment events.
5.2.2
- Update the User Registration & Membership WordPress plugin to version 5.2.2 or later through the WordPress admin dashboard under Plugins > Installed Plugins, or via FTP/wp-cli by replacing the plugin files with the updated version from wordpress.org
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11964 — 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-11964 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