Crypto <= 2.15 - Cross-Site Request Forgery to Authentication Bypass
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- 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-352.
Summary
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 it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- 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-9990
- 2026-10-03 Alias added: GHSA-mvwj-4mhx-2qqv
References
More odude Crypto Tool vulnerabilities
- TI-2024-09272 Crypto <= 2.18 - Authentication Bypass via log_in CVSS 3.1CRITICAL 9.8
- TI-2024-09271 Crypto <= 2.19 - Authentication Bypass via register CVSS 3.1CRITICAL 9.8
Sources
- CVE-2024-9990 · CVE Program
- CVE-2024-9990 · NVD
- FIRST EPSS
- GHSA-mvwj-4mhx-2qqv · 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