Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Web Vulnerabilities·Updated Nov 12, 2026

CVE-2020-36847 Scanner

CVE-2020-36847 Scanner - Remote Code Execution (RCE) vulnerability in WordPress Simple File List

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
4.4k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
9.8
CVSScritical
Exploitable remotely over the internet · no authentication required.
Description

The Simple-File-List Plugin for WordPress is vulnerable to Remote Code Execution in versions up to, and including, 4.2.2 via the rename function which can be used to rename uploaded PHP code with a png extension to use a php extension. This allows unauthenticated attackers to execute code on the server.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
Simple File Listby eemitch
AFFECTED< 4.2.3→SAFE ✓≥ 4.2.3
Updated Nov 12, 2026View on NVD →
Detail

The WordPress Simple File List is a popular plugin used by website administrators to manage file uploads and downloads directly from their WordPress dashboard. It is commonly employed by businesses and individual users who require a simple interface to manage files shared through their WordPress site. The plugin allows users to add, delete, list, and rename files within designated directories. Despite its utility, improper configuration and a lack of robust security measures can expose a site to vulnerabilities. Therefore, maintaining up-to-date versions of such plugins is crucial to ensure the security of the website. Often, vulnerabilities in plugins like this can be leveraged to compromise the hosting server.

The vulnerability in the WordPress Simple File List plugin enables remote code execution, potentially allowing attackers to execute arbitrary code on the server. This exploit affects versions of the plugin prior to 4.2.3, which includes improperly validated input parameters and a security gap in the nonce checks. Exploiting the vulnerability can be done without authentication, significantly increasing the risk. Attackers may leverage this flaw to upload malicious payloads that could lead to unauthorized access or further exploitation of server resources. It is important to understand the nature of this vulnerability to apply necessary patches promptly.

The technical details of this vulnerability reveal that the issue arises from a lack of proper nonce validation in the plugin's scripts. Specifically, the files ee-upload-engine.php and ee-file-engine.php register their nonce checks too late in the WordPress lifecycle. This delay renders the security checks ineffective, allowing attackers to exploit this gap. Attackers can upload a PHP shell disguised as a PNG file using the ee-upload-engine.php endpoint. Subsequently, they can rename the file using the ee-file-engine.php endpoint to a PHP file for execution. This exploit could lead to complete server takeover if executed successfully.

The potential effects of exploiting this vulnerability are serious, including unauthorized access to the server and the ability to execute arbitrary commands. Such access can lead to data breaches where sensitive information is stolen. Attackers may also use the server to perform lateral movements, further compromising other connected systems. The server could also be used as a platform for additional attacks on other networks. Moreover, once a server is compromised, it can be weaponized for large-scale activities such as deploying botnets or serving as part of a larger malware distribution network. The ramifications of such exploitations predispose the server to long-lasting security and trust issues.

REFERENCES

Solution Advice
  • Update the WordPress Simple File List plugin to version 4.2.3 or later to ensure all security patches are applied.
  • Regularly audit WordPress installations and associated plugins for known vulnerabilities.
  • Implement security plugins that enforce stricter upload policies to prevent similar vulnerabilities.
  • Utilize web application firewalls to monitor and block exploit attempts.
  • Ensure that your WordPress instance is configured with the least privilege principle for all users and processes.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.