Crypto <= 2.19 - Authentication Bypass via register
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-288.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2024-9988
- 2026-10-03 Alias added: GHSA-3xw3-m65r-4f37
References
More odude Crypto Tool vulnerabilities
- TI-2024-09272 Crypto <= 2.18 - Authentication Bypass via log_in CVSS 3.1CRITICAL 9.8
- TI-2024-09273 Crypto <= 2.15 - Cross-Site Request Forgery to Authentication Bypass CVSS 3.1HIGH 8.8
Sources
- CVE-2024-9988 · CVE Program
- CVE-2024-9988 · NVD
- FIRST EPSS
- GHSA-3xw3-m65r-4f37 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences