Loading vulnerability…
CVE-2016-4010 is a critical unauthenticated remote code execution vulnerability in Magento Community and Enterprise Editions prior to 2.0.6. The flaw exists in the payment module's handling of serialized data, specifically in the 'additional_information' field, which is merged with payment data without proper validation. Attackers can exploit this by sending crafted serialized PHP objects via the SOAP or REST APIs (enabled by default), leading to PHP object injection. The exploit chain abuses magic methods such as __destruct() and save() in classes like Credis_Client and Magento\Framework\Simplexml\Config\Cache\File, ultimately allowing arbitrary file write in the web-accessible /pub directory and execution of arbitrary PHP code. The vulnerability is present in all default Magento installations and does not require authentication.
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 (magento_unserialize.rb) that exploits a PHP object injection vulnerability (CVE-2016-4010) in Magento 2.0.6 and earlier. The exploit leverages insecure unserialize operations to achieve remote code execution. The module works by creating a fake shopping cart, obtaining a guest cart ID, and then abusing the '/rest/V1/guest-carts/<cart_id>/set-payment-information' endpoint to upload a PHP backdoor to the webroot. Once the backdoor is in place, the attacker can execute arbitrary PHP code on the target server. The module is written in Ruby and is designed to be used within the Metasploit framework. The exploit is operational, providing a working payload (PHP shell) but not offering advanced customization beyond the standard Metasploit payload options. The code is well-structured, with clear separation of functions for each exploitation step, and includes references to the original vulnerability disclosure and related advisories.
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.