dbcve.org
Wpcom MemberWordPress extension · Wpcom

CVE-2024-7493

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-06
Fix available
A fix is available. Upgrade to 1.5.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 WPCOM Member plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.5.2.1. This is due to the plugin allowing arbitrary data to be passed to wp_insert_user() during registration. This makes it possible for unauthenticated attackers to update their role to that of an administrator during registration.

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 WPCOM Member WordPress plugin up to version 1.5.2.1 has a privilege escalation vulnerability where arbitrary data is passed to wp_insert_user() during registration. Unauthenticated attackers can exploit this to register with administrator privileges by specifying an elevated role in the registration request.

MitigationUpdate WPCOM Member plugin to version 1.5.2.2 or later to receive the security patch that properly sanitizes user role data during registration.

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
Wpcom MemberWordPress extension
Affected:< 1.5.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. Confirm WPCOM Member plugin is installed and active
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wpcom Member' in the list. Check that it shows as 'Active'. Alternatively, check for the file wp-content/plugins/wpcom-member/plugin.php
    Affected if The plugin is installed and active, making the vulnerable code reachable
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the Wpcom Member plugin to view its details. Note the version number displayed. Compare this version against the affected range: versions prior to 1.5.3 are vulnerable
    Affected if Installed version is 1.5.2.1 or lower (any version < 1.5.3)
  3. Verify WordPress user registration is enabled
    In WordPress admin, go to Settings > General and check the box 'Anyone can register'. This setting must be enabled for unauthenticated exploitation
    Affected if 'Anyone can register' is enabled in WordPress general settings
  4. Check if WPCOM Member registration form is enabled
    In WordPress admin, go to Wpcom Member > Settings (or similar settings page for the plugin). Look for registration-related settings that control whether the registration form is active and publicly accessible
    Affected if The plugin's registration feature is enabled and publicly accessible to unauthenticated users

A site is affected if it runs Wpcom Member plugin version < 1.5.3, has the plugin active, and has user registration enabled (both WordPress core setting and the plugin's registration feature), allowing unauthenticated attackers to register as administrators.

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 1.5.3 or later
Fixed in 1.5.3
Interim mitigation

Update WPCOM Member plugin to version 1.5.2.2 or later to receive the security patch that properly sanitizes user role data during registration.

Recommended fix High confidence

1.5.3

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WPCOM Member plugin
  4. Click Update Now to update to the latest version (1.5.3 or higher)
  5. Alternatively, use WP-CLI: wp plugin update wpcom-member
  6. Verify the plugin version after update to confirm version 1.5.3 or later is installed

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

Fix this in Wpcom Member Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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