CVE-2025-11986 MEDIUM

CVE-2025-11986: Crypto Tool <= 2.22 - Unauthenticated Information Exposure via Global Authentication State

Vendor Odude
Product Crypto Tool
Weakness CWE-306 · Missing auth
Published November 11, 2025
Last update April 8, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Crypto Tool versions 2.22 and earlier contain a missing authentication mechanism that allows unauthenticated network access to read sensitive information. An attacker can retrieve confidential data without requiring user interaction or special privileges. The vulnerability affects all versions from release through 2.22.

What an attacker can do

03Attacker Capabilities

Read sensitive information from the application without authentication.

Potential impact on your site

04Site Impact

Confidential data stored in or processed by Crypto Tool may be exposed to unauthorized parties.

Conditions required to exploit

05Prerequisites

Network access to the affected Crypto Tool instance; no authentication required.

Key dates

06Disclosure timeline

November 11, 2025 CVE published
April 8, 2026 Record updated