Loading vulnerability…
CVE-2025-2005 affects the Front End Users plugin for WordPress. According to the provided content, all versions up to and including 3.2.32 are vulnerable to arbitrary file upload because the file upload field in the registration form does not properly validate file types. This allows an unauthenticated attacker to submit arbitrary files to the server through the registration workflow. If the uploaded file is placed in a web-accessible location and can be interpreted by the server, this may 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.
3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2025-2005, targeting the WordPress Front End Users plugin (versions up to 3.2.32). The exploit is implemented in Python (exploit.py) and automates the process of discovering registration forms on a target WordPress site, then uploading a PHP web shell via the vulnerable file upload field. The exploit requires the attacker to specify the target URL, a username, and a password for registration. Upon successful exploitation, the shell can be accessed in the WordPress uploads directory, allowing remote command execution via HTTP GET requests. The repository consists of a README.md with detailed usage instructions and the main exploit script (exploit.py). No framework is used; the exploit is standalone and demonstrates the vulnerability with a simple, hardcoded PHP shell payload.
This repository contains a working exploit for CVE-2025-2005, targeting the WordPress Front-End Users plugin (versions <= 3.2.32). The vulnerability is an unauthenticated arbitrary file upload flaw in the plugin's registration form, allowing attackers to upload and execute PHP files (such as web shells) on the server. The exploit is implemented in Python (exploit.py), which scans the target site for registration forms, submits a registration request with a malicious PHP file, and attempts to upload a web shell. The README.md provides detailed vulnerability information, manual exploitation steps, and mitigation advice. The main endpoint of interest is the uploads directory (/wp-content/uploads/ewd_feup_uploads/), where the shell is stored. The exploit is operational, providing a real payload and automating the attack process.
This repository documents and provides a proof-of-concept exploit for CVE-2025-2005, a critical arbitrary file upload vulnerability in the WordPress Front-End Users Plugin (versions <= 3.2.32). The vulnerability allows unauthenticated attackers to upload arbitrary files, such as PHP web shells, via the plugin's registration form. The README.md contains detailed vulnerability information, a manual HTTP PoC, and a Python script that automates the exploitation process by discovering the registration form and uploading a PHP shell. The exploit results in remote code execution if PHP files are executable in the uploads directory. No actual code files are present in the repository; the exploit code is provided as an example in the README. The main endpoints of interest are the registration form URL and the uploads directory where the shell is stored. The repository is intended for educational and authorized security testing purposes only.
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.
3 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.