CVE-2024-9989 json
Crypto <= 2.18 - Authentication Bypass via log_in
published 2y ago modified 4mo ago also EUVD-2024-50268
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.1%
- EPSS 7.1% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- odude crypto_tool 2.19
Is CVE-2024-9989 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
7.11% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- odude Crypto Tool
- odude crypto
Classification
- Weakness
-
- CWE-288 Authentication Bypass Using an Alternate Path or Channel
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/e21bd924-1d96-4371-972a-5c99d67261cc?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/crypto/tags/2.10/includes/class-crypto_connect_ajax_register.php#L33
product
-
plugins.trac.wordpress.org
/browser/crypto/tags/2.10/includes/class-crypto_connect_ajax_register.php#L138
product
- plugins.trac.wordpress.org /changeset/3189945/crypto#file3
Sources
- CVE List CVE-2024-9989
- NVD CVE-2024-9989
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.