dbcve.org
Crypto ToolWordPress extension · Odude

CVE-2024-9990

HIGH · 8.8 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to after 2.16 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Cross-Site Request Forgery in versions up to, and including, 2.15. This is due to missing nonce validation in the 'crypto_connect_ajax_process::check' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 has a CSRF vulnerability in the crypto_connect_ajax_process::check function due to missing nonce validation. Attackers can forge authentication requests to log in as any existing user on the site, including administrators, by tricking admins into clicking malicious links.

MitigationUpdate the Crypto plugin to version 2.16 or later which includes proper nonce validation. Review and test the fix in a staging environment before production deployment.

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.16

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Odude Crypto Tool plugin is installed
    Check WordPress plugins directory (wp-content/plugins/) for 'crypto' folder or list installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if The Odude Crypto Tool plugin is present and active in the WordPress installation
  2. Determine the installed plugin version
    Check the plugin version in the plugin header comment within the main plugin file (e.g., crypto.php) or view details in WordPress admin Plugins page
    Affected if The version number is 2.16 or lower (vulnerable); version is unknown or cannot be determined (assume vulnerable)
  3. Identify if the vulnerable ajax action is accessible
    Check if the WordPress ajax endpoint responds to action=crypto_connect_ajax_process by inspecting the plugin source code for add_action('wp_ajax_crypto_connect_ajax_process'...) or add_action('wp_ajax_nopriv_crypto_connect_ajax_process'...)
    Affected if The ajax action handler for crypto_connect_ajax_process is registered and publicly accessible (wp_ajax_nopriv_) or accessible to authenticated users
  4. Verify nonce validation is missing in the check function
    Examine the plugin source code for the crypto_connect_ajax_process::check function. Look for wp_verify_nonce, check_ajax_referer, or wp_create_nonce calls. If none are present, the vulnerability exists
    Affected if The check function contains no nonce verification calls (wp_verify_nonce, check_ajax_referer, etc.)

The environment is affected if the Odude Crypto Tool plugin version is 2.16 or lower AND the crypto_connect_ajax_process ajax action is registered without proper nonce validation in the check function.

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.16
Interim mitigation

Update the Crypto plugin to version 2.16 or later which includes proper nonce validation. Review and test the fix in a staging environment before production deployment.

Recommended fix High confidence

Crypto Tool version 2.16 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Crypto plugin in the list
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org and upload it
  5. Verify the updated version number reflects the patch (version 2.16 or later)
  6. Test that the plugin functionality works as expected

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

Fix this in Crypto Tool Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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