CVE-2025-11988 affects the Crypto plugin for WordPress in all versions up to and including 2.22. The issue stems from an unauthenticated AJAX action, wp_ajax_nopriv_crypto_connect_ajax_process, which permits invocation of the crypto_delete_json method after only a publicly available nonce check. Because the action is exposed to unauthenticated users and the nonce is not a sufficient authorization control, an attacker can trigger deletion of JSON files matching the pattern *_pending.json in the wp-content/uploads/yak/ directory. The vulnerability results in unauthorized manipulation of application data by allowing deletion of plugin-generated workflow artifacts.
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.
2 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.