The bashMail function in SkyBlueCanvas CMS (versions before 1.1 r248-04) contains a command injection vulnerability. When the pid parameter is set to 4, user-supplied input in the name, email, subject, or message parameters to index.php is not properly sanitized before being passed to a shell command, allowing attackers to inject arbitrary shell metacharacters and execute commands 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 (modules/exploits/unix/webapp/skybluecanvas_exec.rb) that exploits a remote code execution vulnerability (CVE-2014-1683) in SkyBlueCanvas CMS version 1.1 r248-03 and below. The exploit works by sending a specially crafted HTTP POST request to the CMS's index.php endpoint, injecting arbitrary commands via the 'name' parameter. The module supports a variety of command payloads (bash, perl, python, ruby, telnet) and is operational, allowing attackers to execute arbitrary commands on the target server. The module includes a check method to verify if the target is running a vulnerable version. The only endpoints referenced are the CMS installation path (default '/') and the main index.php file. The repository is structured as a typical Metasploit exploit module, written in Ruby, and is intended for use within the Metasploit Framework.
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.