dbcve.org
MemberheroWordPress extension · Najeebmedia

CVE-2024-49604

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to after 5.5 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
Authentication Bypass Using an Alternate Path or Channel vulnerability in N-Media Simple User Registration wp-registration allows Authentication Bypass.This issue affects Simple User Registration: from n/a through <= 6.7.

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

The N-Media Simple User Registration WordPress plugin (wp-registration) versions through 6.7 contains an authentication bypass vulnerability allowing attackers to circumvent normal login mechanisms through an alternate path or channel.

MitigationUpdate the Simple User Registration plugin to the latest patched version immediately, and audit user accounts for unauthorized access since exploitation.

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:<= 5.5

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. Check if Simple User Registration plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Simple User Registration' by Najeebmedia, or inspect the /wp-content/plugins directory for a folder containing 'registration' in the name
    Affected if Plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Simple User Registration and read the version number from the plugin row, or open the main plugin file (e.g., wp-registration.php) and check the 'Version' header comment
    Affected if Version number is 5.5 or lower
  3. Verify user registration functionality is active
    Check WordPress admin > Simple User Registration settings page, or inspect whether the registration endpoint (/wp-login.php?action=register or custom registration URL) responds and allows new user submissions
    Affected if User registration form is accessible and functional on the site

If the Simple User Registration plugin is installed with version 5.5 or lower and user registration is enabled, the environment is affected by CVE-2024-49604 and vulnerable to authentication bypass.

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 5.5
Interim mitigation

Update the Simple User Registration plugin to the latest patched version immediately, and audit user accounts for unauthorized access since exploitation.

Recommended fix Moderate confidence

Latest available version of Simple User Registration plugin (version 6.8 or higher)

  1. 1. Log in to the WordPress admin dashboard.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the 'Simple User Registration' (or 'wp-registration') plugin by N-Media.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is functioning correctly and test user registration functionality.

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

Fix this in Memberhero Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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 locally
dbcve dependency scanner

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