Simple File ListWordPress extension · Simplefilelist
CVE-2020-36847
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Simple-File-List WordPress plugin (versions up to 4.2.2) contains an unauthenticated Remote Code Execution vulnerability in its rename function. Attackers can upload files with PHP code disguised as .png images, then rename them to .php extension, allowing arbitrary code execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Simple File ListWordPress extension
< 4.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Simple File List plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Simple File List'. Check the version number displayed. Alternatively, inspect the plugin main file (simple-file-list/simple-file-list.php) and look for the 'Version:' header comment.Affected if The installed version is less than 4.2.3 (e.g., 4.2.2, 4.2.1, 4.2.0, etc.)
-
Confirm plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify that Simple File List shows as 'Active'. An inactive plugin may still have files present but is not processing requests.Affected if The plugin is active and the version is below 4.2.3
-
Inspect upload directory for suspicious PHP filesNavigate to the plugin's upload directory (typically wp-content/uploads/simple-file-list/ or similar). List all .php files. Check file creation timestamps. Any .php files present in this directory that were not deliberately placed there are highly suspicious.Affected if Any .php files exist in the upload directory, especially if created around the time of potential exploitation (check timestamps)
-
Search for renamed PHP files disguised as imagesReview recently added .png or .jpg files in the upload directory that have anomalous characteristics: unusually large file size (indicating embedded PHP code), or files with double extensions (e.g., file.png.php). Use 'ls -la' or file manager to examine file metadata.Affected if Large .png/.jpg files or files with double extensions are present that were not intentionally uploaded as images
-
Check server access logs for rename operationsReview web server access logs (Apache error/access logs or Nginx access logs) for POST requests to the file rename endpoint. Look for patterns like '/?sfl-action=rename' or '/wp-admin/admin-ajax.php?action=sfl_rename' with unusual parameters. Filter for requests from unexpected IP addresses.Affected if Log entries show unauthorized rename operations on the Simple File List endpoint, especially from unauthenticated sources
A system is affected if the Simple File List plugin version is below 4.2.3 AND the plugin is active, with potential indicators including suspicious PHP files or rename operations in the upload directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.2.3
Immediately update the plugin to a patched version if available; otherwise, deactivate and remove the plugin. If the site shows signs of compromise, conduct a full forensic review and reinstall WordPress core files and all plugins from trusted sources.
Simple File List 4.2.3
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate Simple File List plugin
- If update available, click 'Update Now' to upgrade to version 4.2.3
- If no update notification, manually download version 4.2.3 from wordpress.org/plugins/simple-file-list/
- Deactivate and delete the current plugin, then upload and activate version 4.2.3
- Verify the plugin version is showing 4.2.3 in the plugins list
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Simple File List
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-36847 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data