Loading vulnerability…
CVE-2015-10140 affects the WordPress Ajax Load More plugin before version 2.8.1.2. The plugin fails to enforce proper authorization checks on certain AJAX actions, allowing any authenticated user account, including low-privileged roles such as Subscriber, to invoke functionality intended for more privileged users. As a result, an authenticated attacker can upload arbitrary files and delete arbitrary files through the vulnerable AJAX endpoints.
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 (wp_ajax_load_more_file_upload.rb) that exploits an arbitrary file upload vulnerability in the WordPress Ajax Load More plugin (version 2.8.1.1, CVE-2015-10140). The exploit requires valid WordPress credentials and targets the admin-ajax.php endpoint to upload a PHP payload (default.php) using the vulnerable 'alm_save_repeater' action. After uploading, the payload is executed by accessing it via the plugin's repeater directory. The module is weaponized, allowing for customizable payloads and automated cleanup. The code is written in Ruby and leverages Metasploit's HTTP WordPress and FileDropper mixins. The main attack vector is network-based, targeting web applications running the vulnerable plugin. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single 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.
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.