Filemanagerpro File Manager

The File Manager (wp-file-manager) plugin before 6.9 for WordPress allows remote attackers to upload and execute arbitrary PHP code because it renames an unsafe example elFinder connector file to have the .php extension. This, for example, allows attackers to run the elFinder upload (or mkfile and put) command to write PHP code into the wp-content/plugins/wp-file-manager/lib/files/ directory. This was exploited in the wild in August and September 2020.

File Manager <= 3.0 - Unauthenticated Arbitrary File Upload/Download

File Manager Pro <= 8.3.4 - Authenticated (Subscriber+) Arbitrary File Upload

File Manager <= 7.2.4 - Cross-Site Request Forgery to Local JS File Inclusion

There is a CSRF vulnerability in the mndpsingh287 File Manager plugin 3.0 for WordPress via the page=wp_file_manager_root public_path parameter.

File Manager Pro <= 8.3.9 - Unauthenticated Backup File Download and Upload

File Manager Pro <= 8.3.9 - Cross-Site Request Forgery to Arbitrary File Upload

File Manager <= 7.2.1 - Sensitive Information Exposure via Backup Filenames

mndpsingh287 WP File Manager v6.4 and lower fails to restrict external access to the fm_backups directory with a .htaccess file. This results in the ability for unauthenticated users to browse and download any site backups, which sometimes include full database backups, that the plugin has taken.

File Manager Pro <= 8.3.9 - Unauthenticated Limited JavaScript File Upload

File Manager <= 7.2.5 - Authenticated (Administrator+) Directory Traversal

There is an XSS vulnerability in the mndpsingh287 File Manager plugin 3.0 for WordPress via the page=wp_file_manager_root public_path parameter.

The mndpsingh287 File Manager plugin V2.9 for WordPress has XSS via the lang parameter in a wp-admin/admin.php?page=wp_file_manager request because set_transient is used in file_folder_manager.php and there is an echo of lang in lib\wpfilemanager.php.

WP File Manager < 7.1 - Reflected Cross-Site Scripting (XSS)