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

> Unauthenticated attackers can bypass site-wide access controls and inject data by exploiting an unverified AJAX action in the Crypto Tool plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7q6p-mgv4-5rwc

## What is CVE-2025-11986?

CVE-2025-11986 is a medium-severity authentication bypass vulnerability in odude Crypto Tool, published on 11 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-11986?


## How do I fix CVE-2025-11986?

No fix has been published for CVE-2025-11986 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11986 being exploited?

There is no known exploitation of CVE-2025-11986 in the wild and no public exploit code.

Public exploit code:

- https://github.com/jFriedli/CVE-2025-11986 (github_poc): https://github.com/jFriedli/CVE-2025-11986

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11986 and fix it if it is affected.

What it is: CVE-2025-11986 is a medium-severity authentication bypass vulnerability in odude Crypto Tool, published on 11 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11986 in the wild and no public exploit code.

Affected product: odude Crypto Tool. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11986/ (Markdown: https://insights.sbomify.com/CVE-2025-11986/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11986
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11986
- OSV: https://osv.dev/vulnerability/CVE-2025-11986

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11986/
Summaries are generated and may contain mistakes; the official description above is the record.