Loading vulnerability…
CVE-2017-9101 is a remote code execution vulnerability in PlaySMS 1.4 affecting import.php, the Phonebook import feature. According to the provided content, exploitation involves the User-Agent HTTP header together with PHP code embedded in the name of an uploaded file. The flaw indicates insufficient validation or sanitization of attacker-controlled input that is subsequently interpreted as PHP code by the application, allowing arbitrary code execution 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 (1 hidden).
This repository contains a single Metasploit module (playsms_uploadcsv_exec.rb) that exploits an authenticated file upload vulnerability (CVE-2017-9101) in PlaySMS version 1.4. The exploit targets the phonebook import feature (import.php), allowing an authenticated attacker to upload a malicious CSV file. The payload leverages PHP code embedded in the CSV and the User-Agent HTTP header to achieve remote code execution. The module automates authentication, CSRF token extraction, and the upload process, and by default delivers a PHP Meterpreter reverse shell. The code is written in Ruby and is structured as a standard Metasploit exploit module, making it weaponized and easily customizable for different payloads. The main endpoints targeted are /index.php and its various GET/POST parameters for authentication and file upload.
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.