Loading vulnerability…
CVE-2024-6460 affects the Grow by Tradedoubler WordPress plugin through version 2.0.21. The plugin is vulnerable to Local File Inclusion (LFI) via the component parameter. An attacker can manipulate this parameter to cause the application to include local files from the server. Because the vulnerable include path can reach PHP files, this can result in execution of PHP code contained in those files, turning the LFI condition into code execution under the privileges of the web server process.
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 (1 hidden).
This repository contains a Python exploit script (CVE-2024-6460.py) targeting the 'Grow by Tradedoubler Affiliate Tracker' WordPress plugin versions up to 2.0.21. The exploit leverages an unauthenticated Local File Inclusion (LFI) vulnerability via the 'tm_load_data' AJAX action in /wp-admin/admin-ajax.php. The script first checks the plugin version by reading its readme.txt, then logs into WordPress using provided credentials, and finally sends a crafted POST request to retrieve arbitrary files from the server (defaulting to wp-config.php). The README.md provides usage instructions. The main endpoints involved are /wp-content/plugins/tradedoubler-affiliate-tracker/readme.txt (for version check), /wp-login.php (for authentication), and /wp-admin/admin-ajax.php (for exploitation). The exploit is operational, requiring valid credentials and a vulnerable plugin version, and provides file disclosure from 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.
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.