Crypto Tool
Approved changes feed: RSS · Atom
cpe:2.3:a:odude:crypto_tool:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Odude (8aaba358-054d-50e8-a6f0-fd17ca289fa3) |
|---|---|
| Product | Crypto Tool (485563e9-79ed-5f3f-bad5-7f00341d3572) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-11988 |
vulnerable | 2026-06-08 07:04:29.513289 |
Crypto Tool <= 2.22 - Missing Authentication to Unauthenticated Limited File Deletion
MEDIUM (5.3)
The Crypto plugin for WordPress is vulnerable to unauthorized manipulation of data in all versions up to, and including, 2.22. This is due to the plugin registering an unauthenticated AJAX action (wp_ajax_nopriv_crypto_connect_ajax_process) that allows calling the crypto_delete_json method with only a publicly-available nonce check. This makes it possible for unauthenticated attackers to delete specific JSON files matching the pattern *_pending.json within the wp-content/uploads/yak/ directory, causing data loss and denial of service for plugin workflows that rely on these artifacts.
Published: 2025-11-11T03:30:35.177Z
Updated: 2026-04-08T16:45:20.211Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-11986 |
vulnerable | 2026-06-08 07:04:29.511497 |
Crypto Tool <= 2.22 - Unauthenticated Information Exposure via Global Authentication State
MEDIUM (5.3)
The Crypto plugin for WordPress is vulnerable to Information exposure in all versions up to, and including, 2.22. This is due to the plugin registering an unauthenticated AJAX action (wp_ajax_nopriv_crypto_connect_ajax_process) that allows calling the register and savenft methods with only a publicly-available nonce check and no wallet signature verification. This makes it possible for unauthenticated attackers to set a site-wide global authentication state via a single transient, bypassing all access controls for ALL visitors to the site. The impact is complete bypass of [crypto-block] shortcode restrictions and page-level access controls, affecting all site visitors for one hour, plus the ability to inject arbitrary data into the plugin's custom_users table.
Published: 2025-11-11T03:30:51.073Z
Updated: 2026-04-08T17:32:13.715Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9990 |
vulnerable | 2026-06-08 07:00:29.014349 |
Crypto <= 2.15 - Cross-Site Request Forgery to Authentication Bypass
HIGH (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 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.
Published: 2024-10-29T16:31:30.375Z
Updated: 2026-04-08T17:24:27.759Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9989 |
vulnerable | 2026-06-08 07:00:29.013829 |
Crypto <= 2.18 - Authentication Bypass via log_in
CRITICAL (9.8)
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.
Published: 2024-10-29T16:31:30.912Z
Updated: 2026-04-08T17:29:06.923Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9988 |
vulnerable | 2026-06-08 07:00:29.012835 |
Crypto <= 2.19 - Authentication Bypass via register
CRITICAL (9.8)
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.
Published: 2024-10-29T16:31:29.682Z
Updated: 2026-04-08T17:02:35.796Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.