FileOrganizer <= 1.0.9 - Authenticated (Subscriber+) Arbitrary File Upload
Strategic Overview
- Status
- Patched in 1.1.0
- Affected Plugin
- FileOrganizer – WordPress File Manager
- Affected Version
<= 1.0.9- CVSS
- 7.5High
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2024-7985
At a glance
CVE-2024-7985 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the FileOrganizer WordPress plugin, affecting versions <= 1.0.9. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.0; sites on affected versions should update now. Disclosed October 2024, reported by TANG Cheuk Hei (siunam).
Vulnerability Overview
The FileOrganizer – Manage WordPress and Website Files plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the "fileorganizer_ajax_handler" function in all versions up to, and including, 1.0.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, and permissions granted by an administrator, to upload arbitrary files on the affected site's server which may make remote code execution possible. NOTE: The FileOrganizer Pro plugin must be installed and active to allow Subscriber+ users to upload files.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
FileOrganizer <= 1.0.9 carries this weakness at fileorganizer_ajax_handler, and reaching it takes an account at Subscriber level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For FileOrganizer the fix is 1.1.0: builds <= 1.0.9 are affected, anything from 1.1.0 onward is not.
Remediation
Update to version 1.1.0, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: FileOrganizer 1.1.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in FileOrganizer – WordPress File Manager
- 7.5CVE-2026-11962: FileOrganizer <= 1.1.0 Local File Inclusion
CVE-2026-11962 - 7.5CVE-2024-5599: FileOrganizer <= 1.0.7 Sensitive Information Exposure
CVE-2024-5599 - 7.2CVE-2026-6382: Multiple Plugins <= Multiple Versions RCE
CVE-2026-6382 - 7.2CVE-2024-11010: FileOrganizer <= 1.1.4 Local JavaScript File Inclusion
CVE-2024-11010 - 4.4CVE-2024-2324: FileOrganizer and FileOrganizer Pro <= 1.0.6 Stored XSS
CVE-2024-2324 - 2.7CVE-2023-3664: FileOrganizer <= 1.0.3 Arbitrary File Access
CVE-2023-3664
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C