CVE-2024-9990: The Crypto plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including,

Q: How do I fix CVE-2024-9990?

crypto tool: upgrade to newer than 2.16. Exact commands for each OS are on this page.

Q: Is CVE-2024-9990 being exploited?

CVE-2024-9990 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-9990 affect?

CVE-2024-9990 affects crypto tool. Severity is high (CVSS 8.8). 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 una

Routine

HIGH 8.8UPGRADE

CVE-2024-9990 is a high-severity flaw (CVSS 8.8) affecting crypto tool. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 78%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-10-29
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: odude

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-10-29 17:15 UTCPublished CVE record published
2026-06-17 08:25 UTCUpdated Record last modified

odude crypto tool UPGRADE

Affected: <= 2.16

Fixed in: newer than 2.16

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy crypto-tool || rpm -q crypto-tool || crypto-tool --version

2. UPGRADE to newer than 2.16 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade crypto-tool

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade crypto-tool

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-9990?

crypto tool: upgrade to newer than 2.16. Exact commands for each OS are on this page.

Is CVE-2024-9990 being exploited?

CVE-2024-9990 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-9990 affect?

CVE-2024-9990 affects crypto tool. Severity is high (CVSS 8.8). 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 una

How urgent is CVE-2024-9990?

Priority 36/100. High severity

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-9989 CRITICAL 9.8 UPGRADE The Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.18
CVE-2024-9988 CRITICAL 9.8 UPGRADE The Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.19

References

← Back to latest CVEs