Crypto Tool <= 2.22 - Unauthenticated Information Exposure via Global Authentication State

5.3
Missing Authentication for Critical Function
CVE CVE-2025-11986
CVSS 5.3 (Medium)
Publicly Published November 10, 2025
Last Updated July 29, 2026
Researcher Jonas Benjamin Friedli

Description

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.

Learn more about Authentication Bypass vulnerabilities and how to prevent them.

References

Share

Vulnerability Details for Crypto

Software Type Plugin
Software Slug crypto (view on wordpress.org)
Patched? Yes
Remediation Update to version 3.0.0, or a newer patched version
Affected Version
  • <= 2.22
Patched Version
  • 3.0.0

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation