Loading vulnerability…
CVE-2015-10135 affects the WPshop 2 – E-Commerce plugin for WordPress. In versions prior to 1.3.9.6, the plugin's ajaxUpload function does not properly validate uploaded file types, allowing arbitrary file upload. Because the upload functionality can be reached without authentication, an unauthenticated attacker can submit crafted files to the server. If the uploaded file is placed in a web-accessible location and executable by the server, this can lead to 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.
This repository contains a single Metasploit module targeting an arbitrary file upload vulnerability in the WordPress WPshop eCommerce plugin (versions 1.3.3.3 to 1.3.9.5, CVE-2015-10135). The exploit works by sending a specially crafted POST request to the vulnerable 'ajax.php' endpoint within the plugin, uploading a PHP payload. If successful, the payload is then executed by accessing it via the uploads directory, granting remote code execution on the target server. The module is written in Ruby and leverages Metasploit's HTTP and file dropper mixins. The exploit is operational and provides a working method for remote code execution, assuming the target is running a vulnerable version of the plugin. The main endpoints involved are the file upload handler and the uploads directory where the payload is placed.
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.
5 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.