dbcve.org
MemberheroWordPress extension · Najeebmedia

CVE-2025-4334

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-26
Fix available
A fix is available. Upgrade to after 6.3 or later.
See remediation →
100/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
The Simple User Registration plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 6.3. This is due to insufficient restrictions on user meta values that can be supplied during registration. This makes it possible for unauthenticated attackers to register as an administrator.

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 Simple User Registration WordPress plugin (versions up to 6.3) lacks proper validation on user meta values during the registration process. Unauthenticated attackers can supply arbitrary user meta data, including administrator role parameters, to create a privileged admin account during registration.

MitigationUpdate the plugin to the latest version immediately. If an update is unavailable, disable the registration functionality or restrict public registration until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MemberheroWordPress extension
Affected:<= 6.3

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
High

CVSS:3.1/AV:N/AC:L/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. Identify plugin installation
    Locate the Simple User Registration plugin in your WordPress installation (typically in /wp-content/plugins/simple-user-register/ or similar). Check the main plugin file for the version number in the plugin header comment.
    Affected if The plugin is installed and the version is 6.3 or lower
  2. Verify installed version
    Open the main plugin file and locate the 'Version' field in the plugin header. Compare this version number against the affected range (<= 6.3).
    Affected if The installed version is 6.3 or any version lower than 6.3
  3. Confirm public registration is enabled
    Navigate to WordPress Settings > General > Membership (or check plugin settings) and verify if 'Anyone can register' is checked, or check the Simple User Registration plugin settings for open registration enabled.
    Affected if Public/user registration is enabled on the site
  4. Audit admin-level accounts
    Go to WordPress Users panel and review all accounts with Administrator role. Look for newly created accounts you do not recognize, especially those created recently or with generic usernames.
    Affected if Unexpected administrator accounts exist that were not created by legitimate administrators

You are affected if the Simple User Registration plugin version is 6.3 or lower AND public registration is enabled on your site, as this allows unauthenticated attackers to create admin accounts.

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
Upgrade available Upgrade to a release after 6.3
Interim mitigation

Update the plugin to the latest version immediately. If an update is unavailable, disable the registration functionality or restrict public registration until a patch is released.

Recommended fix High confidence

Latest version available in the WordPress plugin repository (version > 6.3)

  1. Update the Simple User Registration plugin to the latest available version from the WordPress plugin repository
  2. After updating, review all user accounts with administrator role to confirm they are legitimate
  3. Audit the plugin settings to ensure only intended roles can be registered
  4. Consider implementing additional access controls or a web application firewall as a precautionary measure

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

Fix this in Memberhero Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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