Handlebars versions before 4.3.0 contain a prototype-pollution vulnerability in template processing. A crafted template can modify an object's proto and defineGetter properties, enabling manipulation of JavaScript object behavior that can be leveraged to execute arbitrary code.
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 provides both an exploit and a scanner for CVE-2019-19919, a remote code execution vulnerability in Handlebars (Node.js template engine) versions prior to 4.5.3. The exploit (handlebars_exploit.py) allows a user to specify a target URL and an OS command, then crafts and sends a malicious Handlebars template via HTTP POST to the target. If the backend is vulnerable, the command is executed on the server and the output is returned. The scanner (handlebars_scanner.py) can check a target for the presence and version of Handlebars, and optionally test for injection vulnerabilities using a non-destructive payload. The repository is structured with clear separation between exploitation and detection, and is written in Python. The main attack vector is network-based, targeting web applications that render user-supplied Handlebars templates. The exploit is operational, providing a working payload and requiring only the target URL and desired command from the user.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.