Loading vulnerability…
A remote code execution vulnerability exists in the WordPress File Upload plugin (all versions up to and including 4.24.12) due to improper handling of the 'wfu_ABSPATH' cookie parameter. This allows unauthenticated attackers to execute arbitrary code 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.
Repository contains a Python proof-of-concept exploit for CVE-2024-11635 affecting the WordPress plugin "WP File Upload" (versions <= 4.24.12). The main executable is a single Python script named `exploit` that: - Normalizes a target base URL (rhost) and optionally a custom WordPress root path. - Checks whether the plugin directory is reachable and then fetches `/wp-content/plugins/wp-file-upload/readme.txt` to extract the installed version using a regex. - Proceeds to exploitation (method `exploitation()` is referenced; the provided snippet is truncated, but the surrounding code and README indicate it abuses the `wfu_ABSPATH` cookie parameter to reach an unauthenticated code execution path). - Builds a PHP filter-chain payload (`php://filter/...`) consistent with techniques used to generate/transform PHP code into an executable primitive (README and comments reference Synacktiv’s php_filter_chain_generator). The intended end state is command execution (e.g., `system($_GET['cmd']);`) with attacker-controlled commands. Notable exploit capabilities: - Unauthenticated RCE against vulnerable WP File Upload installations. - Version check / vulnerability gating (compares extracted version to 4.24.12). - Optional proxy support and optional SSL verification disabling. Repository structure/purpose: - `exploit`: Python network exploit/PoC implementing detection (version check) and exploitation logic. - `readme.md`: Documentation, impact, usage instructions, and references; explicitly states the vulnerable vector is the `wfu_ABSPATH` cookie parameter. - `safe-lab/docker_compose.yaml`: A controlled lab environment (WordPress + MariaDB) for safe reproduction; exposes WordPress on port 80 and provides default DB credentials for the lab. Overall, this is an operational PoC exploit (not a framework module) intended for controlled testing of CVE-2024-11635, with a built-in version enumeration step and a payload strategy aimed at achieving arbitrary command execution on the target server.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.