Loading vulnerability…
WP Umbrella: Update Backup Restore & Monitoring for WordPress versions through 2.17.0 contains a local file inclusion vulnerability in the filename parameter processed by the umbrella-restore action. An unauthenticated attacker can cause arbitrary server-side files to be included and executed. If attacker-controlled files, including uploads nominally treated as safe file types, can be included, the issue can result in execution of PHP code.
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-12209, targeting the WP Umbrella 'Update Backup Restore & Monitoring' WordPress plugin (versions <= 2.17.0). The exploit leverages an unauthenticated local file inclusion (LFI) vulnerability by sending a specially crafted HTTP GET request to the target, using the 'umbrella-restore' and 'filename' parameters to traverse directories and read arbitrary files from the server. The main file, 'CVE-2024-12209.py', accepts the target URL and the desired file path as arguments, then prints the contents of the file if the exploit is successful. The repository also includes a brief README describing the vulnerability. No payload is delivered beyond file reading, and no authentication is required, making this a straightforward POC for LFI exploitation.
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.