CVE-2013-10051 is a remote code execution vulnerability affecting InstantCMS 1.6 and earlier. The flaw is in the search view handler, where user-controlled input from the look parameter is incorporated into an eval() call without proper sanitization. Because the application concatenates attacker-supplied data into a PHP expression and executes it, a remote attacker can trigger arbitrary PHP execution by sending a crafted HTTP GET request. The provided description further indicates the exploit uses a base64-encoded payload delivered in the Cmd header, which is then executed in the context of the vulnerable web application.
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 (modules/exploits/unix/webapp/instantcms_exec.rb) that exploits a remote PHP code execution vulnerability in InstantCMS version 1.6 and prior (CVE-2013-10051). The exploit leverages a dangerous use of eval() in the target application, allowing an attacker to execute arbitrary PHP code by sending a specially crafted HTTP GET request. The payload is delivered via a base64-encoded string in the 'Cmd' HTTP header, which is then decoded and executed on the server. The module includes a check method to verify vulnerability by looking for 'Build Date' in the phpinfo() output. The only required configuration is the URI path to the InstantCMS instance, which defaults to '/'. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The main attack vector is network-based, targeting the web application over HTTP.
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.
6 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.