Loading vulnerability…
CVE-2025-11170 is an arbitrary file upload vulnerability in the WP移行専用プラグイン for CPI plugin for WordPress. According to the provided content, the issue is caused by missing file type validation in the Cpiwm_Import_Controller::import function and affects all versions up to and including 1.0.2. Because uploaded files are not properly restricted by type, an unauthenticated attacker can upload arbitrary files to the server hosting the affected WordPress site. 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 Python exploit script (CVE-2025-11170.py) targeting CVE-2025-11170, a critical unauthenticated arbitrary file upload vulnerability in the 'WP移行専用プラグイン for CPI' WordPress plugin (versions <= 1.0.2). The exploit automates the process of uploading a file (default: a PHP webshell) to the vulnerable server by sending a crafted POST request to the '/wp-admin/admin-ajax.php' endpoint, leveraging the plugin's lack of file type validation. Upon successful exploitation, the script outputs the URL path to the uploaded file (e.g., '/wp-content/plugins/cpi-wp-migration/storage/shell.php'), which can then be accessed to execute arbitrary commands on the server. The repository also includes a README with detailed usage instructions, a license file, and a requirements.txt listing Python dependencies. The exploit is operational, providing a working webshell payload and robust error handling, but is not part of a larger exploitation framework.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.