dbcve.org
Crypto ToolWordPress extension · Odude

CVE-2024-9989

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.18. This is due to a limited arbitrary method call to 'crypto_connect_ajax_process::log_in' function in the 'crypto_connect_ajax_process' 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 WordPress plugin (versions up to 2.18) contains an authentication bypass vulnerability in its AJAX handler. The 'crypto_connect_ajax_process' function allows unauthenticated attackers to invoke the 'log_in' method directly, bypassing normal authentication checks. This enables login as any known username, including administrator accounts.

MitigationUpdate the Crypto plugin to the latest patched version once released, or disable the plugin until a patch is available. If immediate patching is not possible, consider restricting AJAX endpoint access via web server configuration or removing the plugin.

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. Verify Crypto plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Crypto' or 'Odude Crypto Tool' in the list of active plugins.
    Affected if The Crypto plugin appears in the installed plugins list
  2. Check installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, find the Crypto plugin and note the version number displayed below the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/crypto/crypto.php for the 'Version' tag.
    Affected if The version is 2.15 or lower, or shows as any version up to 2.18 (vulnerable range)
  3. Confirm AJAX handler vulnerability exists
    Inspect the file wp-content/plugins/crypto/includes/ajax.php (or similar path within the plugin) and search for the function 'crypto_connect_ajax_process'. Verify it contains a callable 'log_in' method that can be invoked without authentication.
    Affected if The function 'crypto_connect_ajax_process' exists and contains a 'log_in' method accessible via AJAX without authentication checks
  4. Test AJAX endpoint accessibility
    Send a crafted POST request to your site's /wp-admin/admin-ajax.php with action=crypto_connect_ajax and a log_in method parameter. Example: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=crypto_connect_ajax&method=log_in&username=admin'
    Affected if The endpoint responds and processes the request without requiring authentication (returns success or accepts the username parameter)

If the Crypto plugin version is 2.15 or lower and the vulnerable AJAX handler with the log_in method is present and accessible, the site is affected by this 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 2.15
Interim mitigation

Update the Crypto plugin to the latest patched version once released, or disable the plugin until a patch is available. If immediate patching is not possible, consider restricting AJAX endpoint access via web server configuration or removing the plugin.

Recommended fix Moderate confidence

Upgrade to Crypto Tool plugin version 2.19 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Crypto Tool' plugin in the list
  4. Click 'Update now' if an update is available, or click 'Delete' and reinstall the latest version from the WordPress plugin repository
  5. Verify the plugin version is updated to version 2.19 or higher

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
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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