webdesi9 file-manager CVE-2020-25213 is a vulnerability in Webdesi9 File Manager
Published on September 9, 2020

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.

NVD

Known Exploited Vulnerability

This WordPress File Manager Remote Code Execution Vulnerability is part of CISA's list of Known Exploited Vulnerabilities. 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.

The following remediation steps are recommended / required by May 3, 2022: Apply updates per vendor instructions.

Vulnerability Analysis

CVE-2020-25213 can be exploited with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. It has the highest possible exploitability rating (3.9). The potential impact of an exploit of this vulnerability is considered to be critical as this vulnerability has a high impact to the confidentiality, integrity and availability of this component.

What is an Unrestricted File Upload Vulnerability?

The software allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment.

CVE-2020-25213 has been classified to as an Unrestricted File Upload vulnerability or weakness.


Products Associated with CVE-2020-25213

You can be notified by stack.watch whenever vulnerabilities like CVE-2020-25213 are published in these products:

Webdesi9 File Manager
 

What versions of File Manager are vulnerable to CVE-2020-25213?