Loading vulnerability…
SP Project & Document Manager for WordPress before version 4.22 contains an insufficient file-upload restriction. The plugin attempts to block PHP and similar server-executable files by checking the uploaded file extension, but the check is case-sensitive. An attacker able to upload a file can bypass the restriction by using a mixed-case extension such as .pHP, allowing upload of a PHP file that may be executable by the server.
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 targeting an authenticated remote code execution vulnerability (CVE-2021-24347) in the WordPress plugin SP Project & Document versions prior to 4.22. The exploit requires valid admin credentials for the target WordPress site. It abuses an arbitrary file upload flaw, where the plugin's file extension check is case-sensitive and can be bypassed by uploading a file with a mixed-case extension (e.g., .pHP). The module logs in, determines the user ID, uploads a PHP payload to the plugin's upload endpoint, and then triggers the payload by sending a GET request to the uploaded file's location. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The main endpoints involved are the plugin's file upload handler and the uploads directory where the payload is executed. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.
1 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.