Loading vulnerability…
Subscribe to Comments for WordPress through version 2.1.2 contains a local file inclusion vulnerability in processing of the Path to header value. An authenticated administrator can cause arbitrary server-side files to be included and executed. Where includable files contain PHP code, the flaw enables execution of that 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.
This repository contains a single Metasploit auxiliary module targeting a directory traversal vulnerability (CVE-2015-10133) in the WordPress 'Subscribe to Comments' plugin version 2.1.2. The exploit requires valid WordPress user credentials and leverages the plugin's options page to perform an authenticated file read attack. The attacker can specify any file path (default: /etc/passwd) to read files accessible by the web server. The module handles authentication, nonce retrieval, and the file read process, saving the output for the attacker. The code is written in Ruby and is structured as a typical Metasploit module, making it easy to use within the framework. The main endpoints targeted are the WordPress admin options pages related to the vulnerable plugin.
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.
6 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.