Crypto vulnerabilities
Plugin slug crypto · 5 known vulnerabilities · latest disclosed 2025-11-10 · WordPress.org page
Every listed vulnerability has a fix. Version 3.0.0 or later is not affected by any of them. If your site runs an older version, update it.
3 of 5 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Crypto
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 5.3 | <= 2.22 | 3.0.0 | CVE-2025-11986 | 2025-11-10 | Advisory |
| Medium 5.3 | <= 2.22 | 3.0.0 | CVE-2025-11988 | 2025-11-10 | Advisory |
| Critical 9.8 | <= 2.19 | 2.20 | CVE-2024-9988 | 2024-10-28 | Advisory |
| High 8.8 | <= 2.15 | 2.16 | CVE-2024-9990 | 2024-10-28 | Advisory |
| Critical 9.8 | <= 2.18 | 2.19 | CVE-2024-9989 | 2024-10-28 | Advisory |
Check if a site is affected
Enter a site address to see which version of Crypto and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Crypto plugin safe to use?
All 5 known issues are fixed in current versions (3.0.0 or later). Keeping it updated is what matters.
How do I check which version of Crypto my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.