Loading vulnerability…
In Pluck CMS versions before 4.7.7-dev2, the endpoint /data/inc/images.php permits an attacker to upload a file with the image/jpeg content type while using a .htaccess filename. This can be abused to place attacker-controlled directives and subsequently enable upload/execution of arbitrary PHP code, resulting in remote code execution.
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 is a proof-of-concept exploit for CVE-2018-11736, targeting Pluck CMS versions prior to 4.7.7-dev2. The exploit is implemented in Rust (src/main.rs) and automates the process of uploading a malicious .htaccess file and a fake image containing PHP code to a vulnerable Pluck CMS instance. The .htaccess file reconfigures the web server to treat .jpg files as PHP scripts, enabling remote code execution when the attacker accesses the uploaded image. The exploit requires a valid authenticated session (session cookie) and the base URL of the target. The repository includes a Dockerfile and docker-compose.yaml for setting up a vulnerable test environment, as well as example payload files (.htaccess and test.jpg). The main attack vector is network-based, exploiting the file upload functionality of the CMS. The exploit demonstrates successful RCE by uploading and executing a PHP payload. The code is a functional PoC and not weaponized, but it provides a clear demonstration of the vulnerability and its exploitation process.
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.
4 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.