dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-32488

HIGH · 8.1 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Incorrect Privilege Assignment vulnerability in wpeverest User Registration user-registration allows Privilege Escalation.This issue affects User Registration: from n/a through <= 4.4.9.

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

This is a privilege escalation vulnerability in the User Registration WordPress plugin by wpeverest. The 'Incorrect Privilege Assignment' vulnerability allows authenticated users (or potentially unauthenticated attackers depending on the specific attack vector) to gain elevated privileges beyond what they should normally have, likely through improper handling of user roles or capabilities during the registration or profile update process.

MitigationUpgrade the User Registration plugin to the latest version (after 4.4.9) to obtain the security patch that fixes the improper privilege assignment. Review user accounts with elevated roles after patching to detect any unauthorized privilege escalation.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Verify User Registration plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'User Registration' by wpeverest. Alternatively, check the /wp-content/plugins/ directory for the user-registration folder.
    Affected if The plugin is present in the installation
  2. Check the installed plugin version
    In WordPress admin, click on the User Registration plugin to view its details, or open user-registration/readme.txt and look for the Version: field. Compare this version number against the affected range (versions up to and including 4.4.9).
    Affected if The installed version is 4.4.9 or lower
  3. Confirm user registration functionality is enabled
    Go to User Registration > Settings > General Options and verify if the 'Enable User Registration' setting is turned on, or check if any registration form is published and accessible.
    Affected if User registration is enabled and the plugin version is vulnerable
  4. Audit user accounts for unauthorized elevated roles
    Navigate to Users > All Users in the WordPress admin. Review the listed roles for any accounts (especially those with Subscriber or Contributor roles initially) that now have Administrator or other high-privilege roles that were not intentionally assigned.
    Affected if Unexpected user accounts exist with elevated Administrator or Editor roles that were not manually assigned

A user is affected if the User Registration plugin by wpeverest is installed with version 4.4.9 or lower, user registration is enabled, and unexpected administrator or elevated-privilege accounts are present in the system.

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 the User Registration plugin to the latest version (after 4.4.9) to obtain the security patch that fixes the improper privilege assignment. Review user accounts with elevated roles after patching to detect any unauthorized privilege escalation.

Recommended fix Moderate confidence

Latest version of User Registration plugin (newer than 4.4.9)

  1. 1. Back up your WordPress site (database and files) before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find the 'User Registration' plugin by wpeverest
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, manually download the latest version from wordpress.org/plugins/user-registration/ and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is working correctly and test user registration functionality
  7. 7. Check that user roles and capabilities are functioning as expected to confirm the privilege escalation vulnerability is resolved
Caveat Minor version updates typically have no breaking changes; always review the plugin changelog for any significant changes affecting your setup

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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