VMware vCenter Chargeback Manager versions prior to 2.5.1 contain a vulnerability in the upload handling functionality. The application does not properly validate or sanitize uploaded files, allowing remote attackers to upload and execute arbitrary code on the server via unspecified vectors.
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 VMware vCenter Chargeback Manager 2.0.1 on Windows 2003 SP2, exploiting CVE-2013-3520. The exploit leverages an unauthenticated file upload vulnerability in the ImageUploadServlet, allowing arbitrary JSP files to be uploaded to the web-accessible /cbmui/images/ directory. The module uploads a JSP dropper, which writes and executes a Windows executable payload (such as Meterpreter) on the target system, resulting in remote code execution as a privileged user. The module includes cleanup routines to remove the uploaded webshell after exploitation. The main attack vector is network-based, targeting the HTTP(S) interface of the vulnerable application. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.