CVE-2025-13382
📋 TL;DR
This vulnerability allows authenticated WordPress users with Subscriber-level access or higher to rename files uploaded by other users via the Frontend File Manager Plugin's REST API endpoint. Attackers can exploit this insecure direct object reference to disrupt other users' file access or potentially rename critical files. All WordPress sites using vulnerable versions of this plugin are affected.
💻 Affected Systems
- Frontend File Manager Plugin for WordPress
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Attackers rename critical system files or configuration files, causing service disruption, data loss, or privilege escalation if renamed files are later processed by other vulnerable components.
Likely Case
Malicious users rename other users' uploaded files, causing confusion, disruption of workflows, or denial of service for legitimate users who can't access their renamed files.
If Mitigated
With proper access controls and file ownership validation, impact is limited to minor user inconvenience if attackers can only rename non-critical user files.
🎯 Exploit Status
Exploitation requires authenticated access but is straightforward via API calls with manipulated fileid parameters.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 23.5 or later
Vendor Advisory: https://plugins.trac.wordpress.org/browser/nmedia-user-file-uploader
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Frontend File Manager' and check if update is available. 4. Click 'Update Now' to install version 23.5 or later. 5. Verify plugin is active after update.
🔧 Temporary Workarounds
Disable REST API endpoint
allTemporarily disable the vulnerable '/wpfm/v1/file-rename' endpoint by modifying WordPress REST API routing or using security plugins.
Add to theme functions.php: add_filter('rest_endpoints', function($endpoints){ unset($endpoints['/wpfm/v1/file-rename']); return $endpoints; });
Restrict user roles
allLimit plugin access to trusted users only by modifying user capabilities or using role management plugins.
🧯 If You Can't Patch
- Disable the Frontend File Manager plugin entirely until patched
- Implement web application firewall rules to block requests to /wpfm/v1/file-rename endpoint
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin → Plugins → Installed Plugins for 'Frontend File Manager' version 23.4 or earlier.Check Version:
wp plugin list --name='Frontend File Manager' --field=versionVerify Fix Applied:
After update, verify plugin version shows 23.5 or later in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Multiple POST requests to /wp-json/wpfm/v1/file-rename with different fileid parameters from same user
- Failed file access attempts following rename operations
Network Indicators:
- Unusual volume of API calls to file-rename endpoint
- File rename operations from users not matching file ownership
SIEM Query:
source="wordpress" AND uri_path="/wp-json/wpfm/v1/file-rename" | stats count by src_ip, user🔗 References
- https://plugins.trac.wordpress.org/browser/nmedia-user-file-uploader/tags/23.4/inc/classes/class.rest.php#L20
- https://plugins.trac.wordpress.org/browser/nmedia-user-file-uploader/tags/23.4/inc/classes/class.rest.php#L52
- https://www.wordfence.com/threat-intel/vulnerabilities/id/aa8d5feb-2ae9-44b8-90b5-9fc67226855a?source=cve
