CVE-2024-7135 is a vulnerability in the Tainacan plugin for WordPress, affecting all versions up to and including 0.21.7. The 'get_file' function lacks proper capability checks and is susceptible to directory traversal, allowing authenticated users with Subscriber-level access or higher to read arbitrary files on the server. This can expose sensitive files outside the intended scope of the plugin.
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 proof-of-concept exploit for CVE-2024-7135, targeting the Tainacan plugin for WordPress (versions 0.21.7 and below). The exploit leverages a directory traversal vulnerability in the '/wp-json/tainacan/v2/bg-processes/file' endpoint, which lacks proper capability checks and allows authenticated users (Subscriber or higher) to read arbitrary files from the server. The script first authenticates to the WordPress site using provided credentials, extracts a required nonce from the admin dashboard, and then crafts a request to the vulnerable endpoint with a directory traversal payload to retrieve the contents of a specified file (defaulting to 'wp-config.php'). The repository consists of the main exploit script ('CVE-2024-7135.py') and a README file with usage instructions and vulnerability details. No hardcoded endpoints are present; the script requires the user to supply the target URL and credentials.
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.