Loading vulnerability…
PlaySMS versions before 1.4.3 do not sanitize input received from a malicious string. This improper handling of attacker-controlled input may allow unintended processing by affected application functionality; the specific vulnerable function and resulting security impact are not available.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (playsms_template_injection.rb) that exploits a pre-authentication server-side template injection (SSTI) vulnerability (CVE-2020-8644) in PlaySMS before version 1.4.3. The exploit leverages a flaw in the custom TPL template engine, allowing an attacker to inject PHP code via the username field during login. The injected code is stored and later executed, resulting in remote code execution as the web server user. The module is fully weaponized, supporting customizable payloads (defaulting to php/meterpreter/reverse_tcp) and is designed for unauthenticated exploitation over HTTP. The only endpoints referenced are the PlaySMS web interface (typically /index.php). The code is written in Ruby and structured as a standard Metasploit exploit module, with clear separation of initialization, vulnerability checking, exploitation, and payload delivery.
This repository contains a Python exploit script (exploit.py) and a README for CVE-2020-8644, targeting PlaySMS versions before 1.4.3. The exploit works by sending crafted HTTP requests to the PlaySMS login endpoint, abusing a vulnerability to inject and execute a PHP payload. The payload, when executed, uses /bin/nc.traditional on the target to open a reverse shell to the attacker's machine. The attacker must provide the target's IP and port, as well as their own IP and listening port. The exploit requires the target to have /bin/nc.traditional available. The repository is straightforward, with the main logic in exploit.py and usage instructions in the README. No detection or fake code is present; this is a functional exploit with a customizable payload.
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.