WPLMS for WordPress versions 1.5.2 through 1.8.4.1 contains a privilege-escalation vulnerability in the wp_ajax_import_data AJAX action. An authenticated attacker can alter settings that should be restricted and may be able to create an accessible administrator account.
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 auxiliary module targeting a privilege escalation vulnerability in the WordPress WPLMS theme (versions 1.5.2 to 1.8.4.1, CVE-2015-10139). The exploit requires valid WordPress credentials (any user level) and abuses the 'import_data' function in the theme to set arbitrary WordPress options. The module changes the admin email, enables user registration, and sets the default role to 'administrator'. The attacker is then instructed to register a new account at the default registration page, which will be granted admin privileges. The code is written in Ruby and is structured as a typical Metasploit module, making use of the framework's WordPress HTTP utilities. The main attack vector is network-based, targeting the WordPress admin-ajax.php endpoint. The repository is operational and provides a working privilege escalation exploit, but does not include a customizable payload beyond the described actions.
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.
7 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.