Loading vulnerability…
In Support Incident Tracker (SiT!) version 3.65, the ftp_upload_file.php script exposes sensitive information to remote authenticated users. When a file is uploaded with a crafted file name, the resulting error message reveals the full installation path of the application on the server.
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/sit_file_upload.rb) targeting Support Incident Tracker (SiT!) versions 3.65 and below. The exploit leverages two vulnerabilities (CVE-2011-3829 and CVE-2011-3833) in the SiT! application: one that exposes the upload directory and another that allows arbitrary file uploads due to insufficient validation. The module requires valid user credentials to authenticate to the application. It first determines the upload directory by exploiting an error message, then uploads a PHP payload to the server, and finally executes the payload by making an HTTP request to the uploaded file. The exploit is fully weaponized, allowing the attacker to execute arbitrary PHP code (such as a reverse shell) on the target server. The main endpoints involved are /sit/login.php (for authentication), /sit/ftp_upload_file.php (for file upload), and /sit/index.php (for version checking). The code is written in Ruby and is designed to be used 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.
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.