Loading vulnerability…
CVE-2026-5411 is a high-severity vulnerability in WP Captcha PRO for WordPress affecting all versions up to and including 5.38. The issue is a chained flaw in the plugin's licensing and cloud protection functionality. First, the save_ajax() function does not enforce a sufficient capability check, allowing authenticated users with Subscriber-level access or higher to modify plugin license metadata. An attacker can abuse this to set a malicious value for the cloud protection source location. Second, the sync_cloud_protection() function retrieves an archive from that attacker-controlled location and extracts its contents into a web-accessible uploads directory without adequate validation of file type, archive contents, or filenames. Because the extraction logic permits dangerous file types, an attacker can cause server-side placement of executable PHP content and then invoke it through the web server. The premium plugin is affected; the free plugin sharing the same slug is not directly affected because the vulnerable code path resides in the premium-only licensing module.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.