The GEO my WP WordPress plugin before version 4.5.0.2 contains a vulnerability that allows unauthenticated attackers to include arbitrary files in the PHP execution context. This flaw enables remote code execution (RCE) by allowing attackers to execute arbitrary PHP 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.
This repository contains a Python exploit (exploit-1.py) targeting CVE-2024-6330, a critical unauthenticated Local File Inclusion (LFI) vulnerability in the GEO my WP WordPress plugin (versions <= 4.5.0.1). The exploit leverages the 'form[info_window_template][content_path]' parameter in a POST request to the /wp-admin/admin-ajax.php endpoint, allowing attackers to include and execute arbitrary files on the server. The script automates the exploitation process by iterating over possible object IDs and injecting a command (default: 'id', but customizable) that is executed on the server. The README.md provides a detailed description of the vulnerability, affected versions, and a usage example. The exploit is operational, providing real command execution on the target if successful. Notable endpoints include the vulnerable admin-ajax.php URL, the base WordPress site URL, and an example OAST domain for out-of-band verification. The repository is structured with a single exploit script and a README, and is not part of a larger framework.
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.