Loading vulnerability…
In Cachet versions prior to 2.5.1, the configuration editing feature (such as mail settings) is vulnerable to new line injection by authenticated users, regardless of privilege level. This allows attackers to inject arbitrary code into configuration files, leading to remote code execution on the server. The vulnerability is due to insufficient sanitization of input in the UpdateConfigCommandHandler, which fails to prevent new line characters in configuration values.
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 Python proof-of-concept exploit for CVE-2021-39172, targeting Cachet 2.4. The exploit leverages a Laravel configuration injection vulnerability to achieve remote code execution. The main file, CVE-2021-39172.py, requires the attacker to provide valid credentials for the target Cachet instance, as well as a local Redis server. The script authenticates to the target, injects malicious configuration variables via the /dashboard/settings/mail endpoint, and triggers a reverse shell payload using a crafted PHP object. The payload opens a reverse shell from the target server to the attacker's machine. The repository is structured simply, with one exploit script and a README file. The exploit is operational and demonstrates a real-world attack chain, but is not weaponized for mass exploitation.
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.