Threat Signal Report

Plugin Vulnerability Exposes WordPress Sites to Remote Code Execution

description-logo Description

FortiGuard Labs is aware of a new vulnerability disclosed this week in a WP FIle Manager plugin that will allow for remote code execution (RCE). The WP File Manager plugin is a third party plugin that is installed on over 700,000 WordPress websites globally. It is a file management plugin that allows for the administration of various tasks on the backend, sucn as copy, compression (zip), delete, download, edit, and paste of files on the backend through an easy to use interface. This vulnerability was recently discovered by WordPress vendor Seravo.

What are the specifics of the vulnerability?

Specific details were not disclosed by Seravo at this time; however based on the public writeup, the WP File Manager plugin file at lib/php/connctor.minimal.php will allow for arbitrary file upload and remote code execution when accessed using POST requests.

What is the CVSS score of this vulnerability?


Are there reports of active exploitation in the wild?

Yes, there have been multiple reports of active exploitation observed.

Is there a CVE for this issue?

No, as it is not a vendor specific vulnerability, but a third party plugin. Because of this, there is no CVE assignment for this issue.

What versions of software are affected?

All WordPress sites running the WP File Manager plugin 6.8 and below are affected.

Has the author of the plugin issued a patch?

Yes. Please see the APPENDIX section for a link to the plugin site.

How serious of a vulnerability is this?

HIGH. An attacker can control machines remotely, as well as uploading and performing remote code execution on the affected server. Essentially, the vulnerability can allow an attacker to install malicious software on all the administered devices.

What is that status of AV or IPS coverage?

An IPS signature has been developed for this vulnerability. Customers running the latest definitions (16.921) are protected against this latest issue with the following signature:


AV coverage is not feasible for this event.

What mitigation is available if any?

As a patch is available It is highly recommended to upgrade to version 6.9 as soon as possible. This issue has the highest CVSS score 10 (CRITICAL) allowed and is highly exploitable. If the patch can not be applied to affected devices, organizations should consider using a "virtual patch" once an IPS signature is developed. Please check back here for the IPS signature once it is developed.


Exploit Public-Facing Application

ID: T1190

Tactic: Initial Access

Platform: Linux, Windows


Traffic Light Protocol

Color When Should it Be used? How may it be shared?


Not for disclosure, restricted to participants only.
Sources may use TLP:RED when information cannot be effectively acted upon by additional parties, and could lead to impacts on a party's privacy, reputation, or operations if misused. Recipients may not share TLP:RED information with any parties outside of the specific exchange, meeting, or conversation in which it was originally disclosed. In the context of a meeting, for example, TLP:RED information is limited to those present at the meeting. In most circumstances, TLP:RED should be exchanged verbally or in person.


Limited disclosure, restricted to participants’ organizations.
Sources may use TLP:AMBER when information requires support to be effectively acted upon, yet carries risks to privacy, reputation, or operations if shared outside of the organizations involved. Recipients may only share TLP:AMBER information with members of their own organization, and with clients or customers who need to know the information to protect themselves or prevent further harm. Sources are at liberty to specify additional intended limits of the sharing: these must be adhered to.


Limited disclosure, restricted to the community.
Sources may use TLP:GREEN when information is useful for the awareness of all participating organizations as well as with peers within the broader community or sector. Recipients may share TLP:GREEN information with peers and partner organizations within their sector or community, but not via publicly accessible channels. Information in this category can be circulated widely within a particular community. TLP:GREEN information may not be released outside of the community.


Disclosure is not limited.
Sources may use TLP:WHITE when information carries minimal or no foreseeable risk of misuse, in accordance with applicable rules and procedures for public release. Subject to standard copyright rules, TLP:WHITE information may be distributed without restriction.