Loading vulnerability…
PhpTax version 0.8 is vulnerable to unauthenticated remote code execution in drawimage.php. The vulnerability is caused by unsafe handling of the pfilez GET parameter, which is passed directly to the PHP exec() function without proper sanitization or neutralization of shell metacharacters. An attacker can supply crafted input in pfilez to inject arbitrary operating system commands, which are then executed by the underlying shell in the security 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 (phptax_exec.rb) that exploits a remote code execution vulnerability in PhpTax 0.8 (CVE-2012-10037). The vulnerability exists in the 'drawimage.php' script, where the 'pfilez' GET parameter is unsafely passed to an exec() call, allowing arbitrary command injection. The exploit does not require authentication and targets the web application over HTTP. The module is weaponized, leveraging Metasploit's payload system to deliver a variety of command-based payloads (e.g., reverse shell, bind shell) using languages such as Perl, Ruby, Telnet, or Python. The main endpoints involved are '/phptax/' (for detection) and '/phptax/drawimage.php' (for exploitation). The repository is structured as a single Ruby file compatible with the Metasploit framework, and is intended for use by penetration testers to demonstrate or leverage this vulnerability.
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.