Loading vulnerability…
CVE-2013-10032 is an authenticated remote code execution vulnerability in GetSimpleCMS 3.2.1. The flaw is present in the application's upload.php endpoint, which permits authenticated users to upload files without properly validating file type by MIME type and extension. The upload protection relies on blacklist-based filtering rather than a strict allowlist, enabling an attacker to upload a server-executable file such as a .pht file containing PHP code. By using a crafted request and a polyglot or disguised extension, the attacker can place executable code in the web root and then invoke it directly through the web server, resulting in code execution on the target system.
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 file upload vulnerability in GetSimple CMS (CVE-2013-10032). The exploit requires valid credentials for an authenticated user and targets the /admin/upload.php endpoint to upload a malicious PHP file. Upon successful upload, the module executes the payload by sending a GET request to the uploaded file. The exploit is operational, allowing arbitrary PHP code execution on vulnerable GetSimple CMS installations (version 3.1.2 and earlier). The code is written in Ruby and follows the standard Metasploit module structure, utilizing HTTP requests for authentication, file upload, and payload execution. The main endpoints involved are the admin login and file upload pages of the CMS.
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.
5 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.