Loading vulnerability…
CVE-2025-11986 affects the Crypto plugin for WordPress in all versions up to and including 2.22. The plugin exposes an unauthenticated AJAX action, wp_ajax_nopriv_crypto_connect_ajax_process, that permits invocation of the register and savenft methods using only a publicly available nonce check and without wallet signature verification. Because the action is reachable without authentication and lacks proper verification of the caller’s wallet ownership, an unauthenticated attacker can manipulate a single transient that controls the plugin’s site-wide authentication state. This results in a global access-control bypass for the plugin, including bypass of [crypto-block] shortcode restrictions and page-level access controls. The flaw also allows arbitrary data injection into the plugin’s custom_users table.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.