Loading vulnerability…
A critical vulnerability in DataLife Engine 9.7 allows remote attackers to execute arbitrary PHP code via the 'catlist[]' parameter in engine/preview.php. The flaw is due to improper sanitization of user input, which is passed to a preg_replace() call with the 'e' modifier, enabling code injection and execution. Exploitation requires a template containing a 'catlist' or 'not-catlist' tag. The vulnerable code is present at lines 249 and 253 of preview.php.
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/datalife_preview_exec.rb) that exploits a PHP code injection vulnerability in DataLife Engine 9.7 (CVE-2013-1412). The vulnerability is present in the preview.php script, which insecurely uses preg_replace() with the 'e' modifier, allowing attackers to inject and execute arbitrary PHP code via crafted POST requests. The exploit targets the /engine/preview.php endpoint and requires a template with a [catlist] or [not-catlist] tag to be installed. The module is weaponized, supporting customizable PHP payloads that are base64-encoded and executed on the target. The exploit is executed over HTTP POST requests, making the attack vector network-based. The repository is structured as a standard Metasploit 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.
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.