CVE-2014-9567 is an unrestricted file upload vulnerability in ProjectSend (formerly cFTP) affecting revisions r100 through r561. The flaw is in process-upload.php, which allows an attacker to upload a file with a .php extension into web-accessible upload/files/ or upload/temp/ directories. Because the application does not properly restrict dangerous file types and the uploaded file can subsequently be requested directly over HTTP, an attacker can cause the server to execute arbitrary PHP code contained in the uploaded file.
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 (1 hidden).
This repository contains a single Metasploit module (projectsend_upload_exec.rb) that exploits an unauthenticated arbitrary file upload vulnerability (CVE-2014-9567) in ProjectSend revisions 100 to 561. The exploit targets the 'process-upload.php' endpoint, allowing an attacker to upload a malicious PHP file and execute it, resulting in remote code execution as the web server user. The module is weaponized, supporting customizable PHP payloads (such as reverse shells or Meterpreter sessions) and automatic cleanup of uploaded files. The code is written in Ruby and leverages Metasploit's HttpClient and FileDropper mixins. The main attack vector is network-based, exploiting a web application's file upload functionality. The module is operational and ready 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.