Loading vulnerability…
CVE-2024-52402 is a Cross-Site Request Forgery (CSRF) vulnerability in the Cliconomics Exclusive Content Password Protect WordPress plugin affecting versions through 1.1.0. Based on the provided description, the flaw allows an attacker to induce a privileged user to submit a forged request that results in uploading a web shell to the web server. The available information indicates the issue is rooted in insufficient CSRF protection on a file upload or plugin management action, but specific vulnerable functions or request handlers are not provided in the source content.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python exploit script (CVE-2024-52402.py) targeting a critical vulnerability (CVE-2024-52402) in the WordPress Exclusive Content Password Protect plugin, versions up to and including 1.1.0. The exploit requires valid WordPress credentials and works by logging into the target site, checking the plugin version, and then abusing the plugin's file upload functionality to deploy a PHP web shell (nxploit.php) to the server's uploads directory. Once uploaded, the shell allows remote command execution via HTTP requests. The repository is structured simply, with the main exploit script, a README providing usage and context, and a license file. The attack vector is web-based, leveraging authenticated access to exploit the vulnerable plugin. Several fingerprintable endpoints are present, including plugin-specific paths and the final web shell location. The exploit is operational, providing a working payload and clear instructions for use.
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.