dbcve.org
Crypto ToolWordPress extension · Odude

CVE-2024-9988

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to after 2.15 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 Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.19. This is due to missing validation on the user being supplied in the 'crypto_connect_ajax_process::register' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the username.

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 Crypto plugin for WordPress versions up to 2.19 contains an authentication bypass vulnerability in the 'crypto_connect_ajax_process::register' function due to missing validation on the user parameter. Unauthenticated attackers can supply any existing username (such as an administrator) and gain authenticated access to that account without requiring password authentication.

MitigationUpdate the Crypto plugin to version 2.20 or later. If an update is unavailable, consider disabling the plugin or implementing additional access controls such as IP-based restrictions on the affected endpoint until a patch is available.

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
Crypto ToolWordPress extension
Affected:<= 2.15

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 installed plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate the 'Odude Crypto Tool' or 'Crypto' plugin and note the version number displayed. Compare this version against the affected range (2.15 and below).
    Affected if The installed version is 2.15 or lower.
  2. Identify the vulnerable AJAX action
    In a WordPress setup, the vulnerable function is crypto_connect_ajax_process::register registered via the wp_ajax_nopriv_ hook (for unauthenticated access). Inspect plugin source code or check network requests for admin-ajax.php?action=crypto_connect_ajax_process calls.
    Affected if The AJAX action 'crypto_connect_ajax_process' is registered and accessible to unauthenticated users (wp_ajax_nopriv_).
  3. Verify user registration is enabled
    The vulnerability exploits the registration functionality. Check WordPress general settings: Settings > General > 'Membership: Anyone can register' must be enabled for the attack to work.
    Affected if WordPress user registration is enabled and the Crypto plugin's registration endpoint is exposed.
  4. Audit for suspicious user accounts
    Review WordPress user list (Users > All Users) for newly created accounts with administrative roles that were not intentionally created, or accounts with usernames matching known legitimate users.
    Affected if Unexpected administrative-level accounts exist or legitimate user accounts show unusual last_login timestamps from unknown IP addresses.

A user is affected if the Crypto plugin version is 2.15 or lower AND the vulnerable AJAX endpoint is publicly accessible AND user registration is enabled on the WordPress site.

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

Update the Crypto plugin to version 2.20 or later. If an update is unavailable, consider disabling the plugin or implementing additional access controls such as IP-based restrictions on the affected endpoint until a patch is available.

Recommended fix High confidence

version 2.20 or latest stable release

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Crypto plugin and click 'Update Now' if an update is available, or manually upload version 2.20 or later from wordpress.org
  4. Verify the updated version number reflects 2.20 or higher after update completes

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

Fix this in Crypto Tool Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $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 $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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