CVE-2018-16660 is a command injection vulnerability in the PWS component of Imperva SecureSphere Gateway versions 13.0.0.10 and 13.1.0.10. An attacker with authenticated access can inject arbitrary operating system commands through the vulnerable PWS functionality, resulting in command execution on the underlying host. Based on the available information, the flaw affects vulnerable SecureSphere Gateway installations and permits execution of attacker-controlled OS-level commands.
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 (modules/exploits/linux/http/imperva_securesphere_exec.rb) targeting a command injection vulnerability (CVE-2018-16660) in Imperva SecureSphere versions 13.0, 13.1, and 13.2. The exploit abuses improper sanitization in the PWS service's Python CGI scripts, specifically via the 'installer-address' parameter in requests to the '/pws/impcli' endpoint. The module requires valid agent registration credentials and targets the service over HTTPS (default port 443). It uses Metasploit's command stager to execute arbitrary commands on the target, enabling remote code execution. The code is operational and can be used to gain full control of vulnerable Imperva SecureSphere systems. The repository is structured as a standard Metasploit exploit module, with all logic contained in a single Ruby file.
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.