CVE-2013-10038 is an unauthenticated arbitrary file upload vulnerability in FlashChat versions 6.0.2 and 6.0.4 through 6.0.8. The issue is present in the upload.php endpoint, which does not properly enforce authentication and fails to adequately validate uploaded file types. As a result, a remote attacker can upload a malicious PHP script to the server. If the uploaded file is placed in a web-accessible location and processed by the PHP runtime, the attacker can then request the uploaded script and execute arbitrary code on the target system in the security context of the web server process.
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 (flashchat_upload_exec.rb) that exploits an unauthenticated arbitrary file upload vulnerability in FlashChat versions 6.0.2 and 6.0.4 to 6.0.8 (CVE-2013-10038). The exploit works by uploading a malicious PHP payload to the server via the /upload.php endpoint and then executing it via the /temp/ directory. The module is fully integrated into Metasploit, allowing the user to select and deliver a PHP payload of their choice, resulting in remote code execution as the web server user. The code includes version checking, file upload, and execution logic, and registers the uploaded file for cleanup. The only file in the repository is the Metasploit module itself, written in Ruby.
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.
3 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.