Loading vulnerability…
CVE-2015-9406 is a directory traversal vulnerability in the mTheme-Unus theme for WordPress before version 2.3. The issue is present in css/css.php, which insufficiently restricts user-supplied path input passed through the files parameter. By supplying directory traversal sequences such as .. in that parameter, an attacker can cause the application to access files outside the intended directory scope and read arbitrary files from the underlying server filesystem.
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 scanner module targeting a directory traversal vulnerability (CVE-2015-9406) in the WordPress 'WP Mobile Edition' plugin version 2.2.7. The exploit works by sending a crafted HTTP GET request to the vulnerable 'css.php' file within the 'mTheme-Unus' theme, using the 'files' parameter to perform directory traversal and read arbitrary files from the server. The module allows the user to specify the file path and traversal depth, with '/etc/passwd' as the default target file. If successful, the contents of the file are saved locally. The code is written in Ruby and is structured as a typical Metasploit module, with options for configuration and reporting. The main attack vector is network-based, exploiting a web-accessible PHP file on a vulnerable WordPress installation.
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.
4 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.