CVE-2024-11613 is a critical vulnerability in the WordPress File Upload plugin (all versions up to and including 4.24.15) affecting the 'wfu_file_downloader.php' file. The vulnerability arises from improper sanitization of the 'source' parameter, which allows user-supplied directory paths. This flaw enables unauthenticated attackers to perform remote code execution, arbitrary file read, and arbitrary file deletion on the server.
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 proof-of-concept exploit (poc.php) and a README for CVE-2024-11613, a critical vulnerability in the WordPress File Upload plugin (<= 4.24.15). The exploit is implemented as a PHP web application that allows a user to specify a target WordPress site URL. It targets the vulnerable 'wfu_file_downloader.php' endpoint to perform arbitrary file read (such as extracting wp-config.php) and remote code execution by uploading a PHP shell using a crafted data:// payload. The exploit attempts multiple common WordPress installation paths to maximize success. The payload is a simple PHP web shell that executes commands via the 'cmd' GET parameter. The repository is structured with a single exploit script and a README providing context and usage information. The attack vector is network-based, requiring only HTTP access to the vulnerable endpoint. No detection-only scripts are present; the code is a functional exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 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.