dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-6145

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 5.1.5. This is due to the is_admin_creation_process() method relying solely on the presence of action=createuser in the $_REQUEST superglobal without performing any authentication or capability check. This makes it possible for unauthenticated attackers to bypass the admin approval requirement when registering new accounts via the fallback submission path.

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 plugin for WordPress contains a Missing Authorization vulnerability in the is_admin_creation_process() function. This function relies solely on checking for action=createuser in the $_REQUEST superglobal without verifying user authentication or capability, allowing unauthenticated attackers to bypass admin approval requirements and register new user accounts directly.

MitigationUpdate to version 5.1.6 or later which includes proper authentication and capability checks in the user registration process. If no patched version exists, implement manual authorization checks in the is_admin_creation_process() function to verify user authentication before processing account creation requests.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify plugin installation and version
    Check the installed version of the 'User Registration & Membership' plugin in WordPress by reviewing the plugin files (usually in wp-content/plugins/) or via WordPress admin dashboard under Plugins > Installed Plugins. Look for the version number in the plugin header.
    Affected if The installed version is below 5.1.6 (or if the version cannot be determined and the plugin is present).
  2. Locate the vulnerable function
    Access the WordPress site via file system or FTP and locate the plugin directory. Find the file containing the is_admin_creation_process() function - this is typically in the main plugin PHP file or a related functions file.
    Affected if The function exists in the codebase and processes user registration requests.
  3. Review the function implementation
    Open the file containing is_admin_creation_process() and examine its code. Look for whether it only checks $_REQUEST['action'] == 'createuser' without any authentication or capability verification (such as checking is_user_logged_in(), current_user_can(), or wp_get_current_user()).
    Affected if The function performs only the action=createuser check in $_REQUEST and lacks any authentication verification before processing user creation.
  4. Test for unauthenticated access
    If accessible, send a crafted HTTP POST or GET request to the WordPress site with action=createuser parameter and registration data (such as user-login, user-email, user-pass) without providing any authentication credentials. Observe if a new user account is created without requiring admin approval or login.
    Affected if Unauthenticated requests with action=createuser successfully create user accounts without requiring admin approval or authentication verification.

A user is affected if the User Registration & Membership plugin is installed with a version prior to 5.1.6 and the is_admin_creation_process() function only checks $_REQUEST['action'] without verifying user authentication.

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 to version 5.1.6 or later which includes proper authentication and capability checks in the user registration process. If no patched version exists, implement manual authorization checks in the is_admin_creation_process() function to verify user authentication before processing account creation requests.

Recommended fix Moderate confidence

Version 5.1.6 or later of the User Registration & Membership WordPress plugin

  1. Check your current User Registration & Membership plugin version in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload Plugin or update directly from the Plugins page
  3. Upload/install version 5.1.6 or later of the User Registration & Membership plugin
  4. After update, verify the new version is active in Plugins > Installed Plugins
  5. Test user registration functionality to ensure the admin approval requirement is enforced properly

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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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