Loading vulnerability…
osCommerce through 2.2 RC2a contains a vulnerability in the administrative file manager component at admin/file_manager.php. The file manager permits file upload and file editing operations without sufficient input validation or effective access control. As described, an unauthenticated attacker can send a crafted POST request to upload a .php file containing attacker-controlled code into a web-accessible location. Because the uploaded file is then interpreted by the PHP runtime on the server, the issue results 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 targeting osCommerce 2.2's file manager utility (CVE-2009-20006). The exploit abuses an unauthenticated file upload vulnerability in the admin console's file manager, allowing arbitrary PHP code execution as the webserver user. The module constructs a random PHP filename, uploads a payload via a POST request to the file_manager.php endpoint, and then triggers execution by requesting the uploaded file. The payload is customizable and supports any PHP-based Metasploit payload, such as reverse shells or Meterpreter. The only required configuration is the base URI of the osCommerce installation. The exploit is fully weaponized and part of 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.
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.