PrestaShop versions 1.6.x before 1.6.1.23 and 1.7.x before 1.7.4.4 are vulnerable to an arbitrary file upload vulnerability. Remote attackers can exploit this flaw to upload malicious files, which can then be executed on the server, leading to remote code execution. The vulnerability is due to insufficient validation of uploaded files, allowing attackers to bypass restrictions and upload executable 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 (1 hidden).
This repository provides a working exploit for CVE-2018-19126, a remote code execution vulnerability in PrestaShop Back Office. The exploit chains multiple vulnerabilities, including a directory rename/delete flaw (CVE-2018-19125) and a deserialization bug via the PHP phar wrapper, to achieve RCE. The main exploit script, 'exploit.php', is a standalone PHP script that automates the attack steps: authenticating to the PrestaShop Back Office, uploading a malicious phar file (crafted with a Monolog gadget chain), renaming the upload directory to bypass security checks, and finally triggering the deserialization via a crafted HTTP POST request. The script requires valid Back Office credentials and a vulnerable PrestaShop version. The payload is customizable, allowing execution of arbitrary system commands. The repository is structured simply, with a license, a detailed README explaining the vulnerability and exploitation steps, and the exploit script itself. The attack is performed over HTTP(S) endpoints exposed by the PrestaShop Back Office file manager.
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.
1 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.