CVE-2025-11986

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

2025-11-10 15:07
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 3.0.0
Affected Plugin
Crypto
Affected Version
<= 2.22
CVSS
5.3Medium
Weakness type
CWE-306 · Missing Authentication for Critical Function
CVE
CVE-2025-11986
View all Crypto vulnerabilities

At a glance

CVE-2025-11986 is a medium-severity Missing Authentication for Critical Function vulnerability in the Crypto WordPress plugin, affecting versions <= 2.22. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.0; sites on affected versions should update now. Disclosed November 2025, reported by Jonas Benjamin Friedli.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-306: Missing Authentication for Critical Function

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Remediation

Update to version 3.0.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Crypto 3.0.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C