CVE-2026-2356
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 – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.2 via the 'register_member' function, due to missing validation on the 'member_id' user controlled key. This makes it possible for unauthenticated attackers to delete arbitrary user accounts that newly registered on the site who has the 'urm_user_just_created' user meta set.
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 confidenceIDOR vulnerability in WordPress membership plugin allows unauthenticated attackers to delete arbitrary newly registered user accounts by manipulating the 'member_id' parameter in the 'register_member' function, due to missing server-side validation on this user-controlled key.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if the User Registration & Membership plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'User Registration & Membership' or 'User Registration' plugin in the listAffected if plugin is not present in the installed plugins list
-
Identify the installed plugin versionIn the Plugins list, click on the plugin name or view details to find the version number displayed under the plugin titleAffected if version number is present and is lower than 5.1.3 (e.g., 5.1.2, 5.1.1, 5.0.x, etc.)
-
Verify the registration feature is enabledNavigate to User Registration > Settings > General and check if the 'Enable User Registration' option is turned on, or inspect the plugin settings for any registration-related moduleAffected if registration functionality is enabled and accessible to unauthenticated users
-
Inspect the vulnerable register_member functionAccess the WordPress site files via FTP or file manager, locate the plugin directory (wp-content/plugins/user-registration or similar), and examine the file containing the register_member function for missing member_id validationAffected if the member_id parameter in the register_member function lacks server-side validation checks before being used in delete operations
User is affected if the User Registration & Membership plugin is installed with version lower than 5.1.3 and the registration feature is enabled, allowing unauthenticated access to the vulnerable register_member function.
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 the User Registration & Membership plugin to version 5.1.3 or later which includes proper validation on the member_id parameter to prevent unauthorized account deletion.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2356 — 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-2356 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