Loading vulnerability…
CVE-2011-10013 affects Traq versions 2.0 through 2.3. The vulnerability is in the admincp/common.php script, where flawed authorization logic performs an access check but does not properly halt execution when that check fails. As a result, an unauthenticated attacker can continue into administrator-only code paths. The issue is exploitable through plugins.php, which can be abused to inject arbitrary PHP code and have it executed by the server, resulting in remote code execution.
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/multi/http/traq_plugin_exec.rb) that exploits a remote code execution vulnerability in Traq versions 2.0 to 2.3 (CVE-2011-10013). The exploit targets a broken authorization schema in the admincp/common.php script, allowing an attacker to inject and execute arbitrary PHP code via the /admincp/plugins.php endpoint. The module first checks for a vulnerable Traq installation by requesting /admincp/login.php and looking for a version string. If vulnerable, it injects a PHP payload using a POST request to /admincp/plugins.php and then triggers code execution by sending a GET request to /index.php with the payload delivered in a custom HTTP header. The exploit is weaponized, allowing for customizable PHP payloads and remote code execution on the target server. The only file in the repository is a Ruby script designed for use within 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.
2 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.