CVE-2017-9080 is a remote code execution vulnerability in PlaySMS 1.4. The vulnerability arises from a combination of unrestricted file upload and code injection in the sendfromfile.php component. Specifically, the application fails to properly validate or sanitize the name of uploaded files, allowing attackers to upload a PHP file with executable code. When the file is subsequently accessed, the embedded PHP code is executed on the server, leading to arbitrary code execution. The $filename parameter is directly involved in the exploitation 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 (playsms_filename_exec.rb) that exploits an authenticated code injection vulnerability in PlaySMS version 1.4 (CVE-2017-9080). The exploit targets the sendfromfile.php feature, where an authenticated user can upload a file with a maliciously crafted filename. The filename is processed insecurely, allowing arbitrary PHP code execution. The module automates authentication (requiring valid credentials), CSRF token extraction, and the upload of a file with a PHP payload embedded in the filename. The default payload is a PHP Meterpreter reverse shell, but any compatible PHP payload can be used. The exploit is weaponized, leveraging Metasploit's payload and session management capabilities. The main endpoints targeted are the PlaySMS authentication and file upload features, all accessed via HTTP requests to /index.php with various parameters. 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.