HomeWordPress vulnerabilitiesFrontend File Manager Plugin
Frontend File Manager Plugin vulnerabilities
Frontend File Manager Plugin has 6 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 6
- Active installs
- Not listed
- Latest version
- Unknown
- Last updated
- Unknown
- Most recent
- 6 Oct 2026
This plugin is shown as closed on WordPress.org, so check the vulnerability record and the developer's current information before deciding whether to keep it installed. WordPress.org reason: security issue.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-32577 | High 7.1 | Up to 23.6 | No fix: plugin closed | 1 d ago |
| Arbitrary file deletion CVE-2026-8095 | High 8.1 | Up to 23.6 | No fix: plugin closed | 28 Jun 2026 |
| Broken access control CVE-2026-1280 | High 7.5 | Up to 23.5 | No fix: plugin closed | 28 Jan 2026 |
| Broken access control CVE-2025-13382 | Medium 4.3 | Up to 23.4 | No fix: plugin closed | 25 Nov 2025 |
| Broken access control CVE-2023-7306 | High 7.5 | Up to 21.5 | No fix: plugin closed | 25 Jul 2025 |
| Remote code execution CVE-2016-15042 | Critical 9.8 | Before 1.1 | Fixed in 1.1 | 16 Oct 2024 |
Read the published descriptions
- CVE-2026-32577, 6 Oct 2026
- Unauthenticated Cross Site Scripting (XSS) in Frontend File Manager <= 23.6 versions. CVE record
- CVE-2026-8095, 28 Jun 2026
- The Frontend File Manager Plugin plugin for WordPress is vulnerable to Authenticated Arbitrary File Deletion in versions up to and including 23.6. This is due to a case-sensitive bypass of the wpfm_dir_path parameter sanitization in the wpfm_file_meta_update AJAX handler, where supplying WPFM_DIR_PATH in uppercase evades the unset check and is normalized to wpfm_dir_path by sanitize_key() during update_post_meta(), allowing an attacker to overwrite the stored file path with an arbitrary filesystem path that is then passed directly to unlink() in delete_file_locally() without any directory containment validation. This makes it possible for authenticated attackers with Subscriber-level access to delete arbitrary files on the server, including sensitive files such as wp-config.php, potentially leading to full site takeover. CVE record
- CVE-2026-1280, 28 Jan 2026
- The Frontend File Manager Plugin for WordPress is vulnerable to unauthorized file sharing due to a missing capability check on the 'wpfm_send_file_in_email' AJAX action in all versions up to, and including, 23.5. This makes it possible for unauthenticated attackers to share arbitrary uploaded files via email by supplying a file ID. Since file IDs are sequential integers, attackers can enumerate all uploaded files on the site and exfiltrate sensitive data that was intended to be restricted to administrators only. CVE record
- CVE-2025-13382, 25 Nov 2025
- The Frontend File Manager Plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 23.4. This is due to the plugin not validating file ownership before processing file rename requests in the '/wpfm/v1/file-rename' REST API endpoint. This makes it possible for authenticated attackers, with Subscriber-level access and above, to rename files uploaded by other users via the 'fileid' parameter. CVE record
- CVE-2023-7306, 25 Jul 2025
- The Frontend File Manager Plugin plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the wpfm_delete_multiple_files() function in all versions up to, and including, 21.5. This makes it possible for unauthenticated attackers to delete arbitrary posts. CVE record
- CVE-2016-15042, 16 Oct 2024
- The Frontend File Manager (versions < 4.0), N-Media Post Front-end Form (versions < 1.1) plugins for WordPress are vulnerable to arbitrary file uploads due to missing file type validation via the `nm_filemanager_upload_file` and `nm_postfront_upload_file` AJAX actions. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible. CVE record
What to do if you run Frontend File Manager Plugin
If you run Frontend File Manager Plugin, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Frontend File Manager Plugin vulnerabilities
Free. We email you when a new vulnerability is published for Frontend File Manager Plugin, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.