Loading vulnerability…
CVE-2013-10070 is a remote code execution vulnerability in PHP-Charts v1.0. The issue is in wizard/url.php, where user-controlled GET parameter names are passed directly to eval() without sanitization or safe parsing. Because attacker-supplied input is evaluated as PHP code, a remote attacker can craft an HTTP request whose parameter names contain malicious PHP expressions. The provided content indicates that base64-encoded payloads can be embedded in parameter names and then evaluated, enabling arbitrary PHP execution and subsequent system command 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 (modules/exploits/unix/webapp/php_charts_exec.rb) that exploits a remote code execution vulnerability in php-Charts version 1.0 (CVE-2013-10070). The vulnerability exists in the 'wizard/url.php' script, which unsafely calls eval() on user-supplied GET parameters, allowing arbitrary PHP code execution. The module leverages this by sending a specially crafted HTTP GET request with a base64-encoded payload that is decoded and executed on the server. The exploit supports a variety of command-based payloads (e.g., reverse shell, arbitrary command execution) and is fully integrated into the Metasploit framework, allowing for easy customization and use. The only endpoint referenced is the vulnerable 'wizard/url.php' script, typically located under '/php-charts_v1.0/'. The exploit is weaponized, providing reliable remote code execution capabilities against vulnerable targets.
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.