Frontend File Manager & Sharing โ€“ User Private Files <= 1.1.2 - Subscriber+ Arbitrary File Upload

8.8
Unrestricted Upload of File with Dangerous Type
CVE CVE-2022-2356
CVSS 8.8 (High)
Publicly Published July 11, 2022
Last Updated December 2, 2022
Researcher Raad Haddad

Description

The Frontend File Manager & Sharing โ€“ User Private Files plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the upload_doc_callback function in versions up to, and including, 1.1.2. This makes it possible for authenticated attackers, with Subscriber level permissions and above, to upload arbitrary files on the affected sites server which may make remote code execution possible under certain conditions. The plugin adds a Rewrite Rule to the site's .htaccess file in order to ensure that direct file access is not possible. However, deactivation of the plugin or resetting of the .htaccess file would lead to potential for Remote Code Execution. Servers other than Apache may ignore .htaccess files and be vulnerable to RCE.

References

Share

Vulnerability Details for User Private Files โ€“ File Upload & Download Manager with Secure File Sharing

Software Type Plugin
Software Slug user-private-files (view on wordpress.org)
Patched? Yes
Remediation Update to version 1.1.3, or a newer patched version
Affected Version
  • <= 1.1.2
Patched Version
  • 1.1.3

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation