dbcve.org
Ultimate Membership ProWordPress extension · Wpindeed

CVE-2024-43240

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-19
Fix available
A fix is available. Upgrade to after 12.6 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
Improper Authentication vulnerability in azzaroco Ultimate Membership Pro indeed-membership-pro.This issue affects Ultimate Membership Pro: from n/a through <= 12.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

Improper Authentication vulnerability in the Ultimate Membership Pro WordPress plugin (indeed-membership-pro) allows attackers to bypass authentication mechanisms. The CVSS 9.8 score indicates unauthenticated attackers can likely gain administrative or privileged access to the membership system.

MitigationImmediately update Ultimate Membership Pro to the latest version if available, or disable the plugin until a patch is released. Review user accounts for unauthorized access and implement additional authentication controls such as two-factor authentication.

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
Ultimate Membership ProWordPress extension
Affected:<= 12.6

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. Locate the Ultimate Membership Pro plugin installation
    Check your WordPress wp-content/plugins directory for a folder named 'indeed-membership-pro' or 'ultimate-membership-pro'. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to search for 'Ultimate Membership Pro' or 'indeed-membership-pro'.
    Affected if The plugin folder or entry is found in the WordPress plugins directory or admin interface.
  2. Identify the installed plugin version
    In WordPress admin, find the plugin in Plugins > Installed Plugins and look at the version number displayed beneath the plugin name. Alternatively, open the main plugin file (such as indeed-membership-pro.php) in the plugin folder and locate the 'Version' header in the file comments.
    Affected if The version number shown is 12.6 or lower.
  3. Verify the plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the plugin shows as 'Active' (not 'Inactive' or 'Must-Use').
    Affected if The plugin status is Active.
  4. Check for suspicious admin accounts
    Navigate to Users > All Users in WordPress admin and review the user list for any unknown administrators or users with administrative privileges that were not intentionally created.
    Affected if Unexpected admin accounts exist that were not created by legitimate administrators.

Your environment is affected if the Ultimate Membership Pro (indeed-membership-pro) plugin is installed, active, and running version 12.6 or lower.

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

Immediately update Ultimate Membership Pro to the latest version if available, or disable the plugin until a patch is released. Review user accounts for unauthorized access and implement additional authentication controls such as two-factor authentication.

Recommended fix Moderate confidence

Ultimate Membership Pro 12.8 or later (check WordPress plugin repository for latest stable release)

  1. 1. Back up your WordPress site and database before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate 'Ultimate Membership Pro' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update was successful by checking the plugin version after update
  6. 6. Test critical membership flows (registration, login, content access) to ensure functionality

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

Fix this in Ultimate Membership Pro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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