CVE-2012-10025 affects the WordPress plugin Advanced Custom Fields (ACF) version 3.5.1 and earlier. The vulnerability is a remote file inclusion flaw in core/actions/export.php. An unauthenticated attacker can supply a malicious value via the acf_abspath POST parameter, causing the application to include a remote PHP resource when PHP is configured with allow_url_include enabled. Because the included resource is executed by PHP, successful exploitation results in arbitrary code execution in the context 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.
This repository contains a single Metasploit module targeting a remote file inclusion vulnerability (CVE-2012-10025) in the WordPress Advanced Custom Fields plugin (versions 3.5.1 and below). The exploit leverages the export.php script to include a remote PHP file, resulting in remote code execution if the PHP configuration option 'allow_url_include' is enabled. The module is written in Ruby and is structured as a standard Metasploit exploit, using the HttpClient and PHPInclude mixins. It defines two main actions: a check method to verify the presence of the vulnerable plugin, and an exploit method that sends a crafted POST request to export.php with a malicious acf_abspath parameter. The only file in the repository is the Metasploit module itself, and it is fully weaponized, allowing for customizable payloads via the Metasploit 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.
4 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.