Skip to main content
WordPress plugin recordReviewed

WP File Manager vulnerability records, with the root path, roles and shortcodes to read

WP File Manager's WordPress.org listing says it lets you edit, delete, upload, download, zip, copy and paste files and folders directly from the WordPress backend.

Its history includes titles ending "Directory Traversal" and "Unauthenticated Resource Access to Site Backups". Match every range, then read the root path, roles, shortcodes and backups.

WP File Manager vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 16 records for WP File Manager. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 8.0.5

Worked out from data retrieved on .

Every affected range listed in this source for WP File Manager ends before version 8.0.5.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. Multiple elFinder Plugins <= 8.0.4 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 8.0.4

    Patched versions: 8.0.5

    Update to at least version 8.0.5.

  2. File Manager 7.2.2 - 8.0.4 - Unauthenticated Information Exposure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • From version 7.2.2 up to and including 8.0.4

    Patched versions: 8.0.5

    Update to at least version 8.0.5.

  3. Multiple Plugins <= Multiple Versions - Authenticated Remote Code Execution

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions before 8.0.4

    Patched versions: 8.0.4

    Update to at least version 8.0.4.

  4. File Manager <= 7.2.7 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 7.2.7

    Patched versions: 7.2.8

    Update to at least version 7.2.8.

  5. File Manager <= 7.2.5 - Authenticated (Administrator+) Directory Traversal

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.8)
    Affected versions
    • All versions up to and including 7.2.5

    Patched versions: 7.2.6

    Update to at least version 7.2.6.

Show 11 older records
  1. File Manager <= 7.2.4 - Cross-Site Request Forgery to Local JS File Inclusion

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions up to and including 7.2.4

    Patched versions: 7.2.5

    Update to at least version 7.2.5.

  2. File Manager And File Manager Pro (Multiple Versions) - Directory Traversal

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.9)
    Affected versions
    • All versions up to and including 7.2.1

    Patched versions: 7.2.2

    Update to at least version 7.2.2.

  3. File Manager <= 7.2.1 - Sensitive Information Exposure via Backup Filenames

    Published:
    Last updated:
    Severity:
    High (CVSS 8.1)
    Affected versions
    • All versions up to and including 7.2.1

    Patched versions: 7.2.2

    Update to at least version 7.2.2.

  4. WP File Manager <= 7.0 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions before 7.1

    Patched versions: 7.1

    Update to at least version 7.1.

  5. File Manager <= 6.8 - Arbitrary File Upload/Remote Code Execution

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions up to and including 6.8

    Patched versions: 6.9

    Update to at least version 6.9.

  6. WP File Manager <= 6.4 - Unauthenticated Resource Access to Site Backups

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 6.4

    Patched versions: 6.5

    Update to at least version 6.5.

  7. File Manager <= 4.8 - Missing Authorization on AJAX Actions

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.3)
    Affected versions
    • All versions up to and including 4.8

    Patched versions: 4.9

    Update to at least version 4.9.

  8. File Manager <= 3.0 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 3.0

    Patched versions: 3.1

    Update to at least version 3.1.

  9. File Manager <= 3.0 - Unauthenticated Arbitrary File Upload/Download

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions up to and including 3.0

    Patched versions: 3.1

    Update to at least version 3.1.

  10. File Manager <= 3.0 - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions up to and including 3.0

    Patched versions: 3.1

    Update to at least version 3.1.

  11. File Manager <= 2.9 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions before 3.0

    Patched versions: 3.0

    Update to at least version 3.0.

Check WP File Manager on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

What WP File Manager reaches, and who the vendor says uses it

The listing is headed File Manager, and its "How to use" steps name the WP File Manager menu.

Its free features include Backup/Restore, described as "Backup and restore themes files, plugins files,uploads folder and db data on server.", and a Root Directory entry: "With this feature you can access files inside and outside of WordPress".

In the free list, Move/Copy and Archives are features "Admin can" use, and Private Folder and Shortcode are marked "Available only for File Manager Pro Edition". The Pro list says "admin is able to control file operations and hide and lock Files and Folders for user roles" and "User can access frontend using shortcode." On Pro, those settings are where to read who can reach the file manager and which folders it shows.

How the WP File Manager records read: names, ranges and shared titles

Cross-site scripting, directory traversal, file upload and backups recur across the titles.

Some name an access level, such as "Authenticated (Administrator+)"; others include the word "Unauthenticated". Titles name the plugin in more than one way, among them File Manager and WP File Manager, and some begin "Multiple Plugins" or "Multiple elFinder Plugins", so identify each record by its CVE id where it has one, and by its fields.

CVE-2026-19708, whose title ends "Unauthenticated Information Exposure", starts partway through the version line: its affected versions field reads from version 7.2.2 up to and including 8.0.4, with 8.0.5 patched, and changelog entries headed 8.0.5 on the plugin's listing name the same CVE id. 7.2.2 is the patched version for CVE-2024-0761, whose title ends "Sensitive Information Exposure via Backup Filenames" (affected: all versions up to and including 7.2.1; patched: 7.2.2), so a site that reached it for that record sits inside the range of CVE-2026-19708.

Match on the version fields, not on a version written in a title. CVE-2026-6382 has "<= Multiple Versions" in its title, which ends "Authenticated Remote Code Execution"; its affected versions field reads all versions before 8.0.4, with 8.0.4 patched. That release sits inside the range of CVE-2026-85081, whose title ends "Reflected Cross-Site Scripting" (affected: all versions up to and including 8.0.4; patched: 8.0.5).

The changelog on the plugin's WordPress.org listing marks security work in entries such as "Security Fixes." and "Security issue fixed", and an entry reads "Security fixes based on the latest automated security review." Read those entries alongside the update guidance at the top of the history.

Reading WP File Manager's settings on a site you are authorised to review

Each step reads a screen on a site you own or have written permission to review, records what it shows and saves nothing, so "Save Changes" stays unpressed.

The vendor's articles on role access and role restrictions reach the settings by clicking the WP File Manager tab in the WordPress panel and then a Settings tab on the left, and the listing's "How to use" steps follow a click on the WP File Manager menu with "Then do with files what you want to do." So the file manager is open on the way to the settings: touch nothing in it, and do not browse, upload, edit, download or delete anything.

Version and edition

WordPress's Plugins screen documentation gives a plugin's version in its Description column, and says WordPress displays an update notice on that screen when a plugin hosted in the Plugin Directory has a newer version available. 1 min read

Allowed roles

The free edition's own text for "Settings - General" says "admin can give access to user roles to use filemanager", beside the note "This is just a demo screenshot. 1 min read

Path restrictions

The vendor's Root Directory article says that clicking the Root Directory option under WP File Manager shows the default path already there, and warns that a wrong path can lead File Manager to stop working. 1 min read

Upload and edit permissions

Two free settings decide where files end up. 1 min read

Public file exposure

The plugin's shortcode help text says wp_file_manager_admin "will work same as backend WP File Manager" and, of wp_file_manager written with no attributes, that "only Administrator can access it". 1 min read

What a WP File Manager version match leaves open

Matching WP File Manager's version to a range says which records the installed release falls under, and nothing about whether any of them was acted on.

Nor does the version show the path in "Public Root Path", the roles ticked under "Select User Roles to", a page carrying the wp_file_manager_without_login shortcode, or what "Existing Backup(s)" holds.

A WordPress security audit goes further on two of those: it looks for backup archives and copies of wp-config.php left in the web root and checks for directory listings, and it replays requests an administrator makes in plugin settings screens as a subscriber to confirm each is refused.

Frequently asked questions

A record reaches this history by being filed under the slug wp-file-manager in the source data, and that filing does not tell you whether it also applies to File Manager Pro. CVE-2023-6825 has a title naming both, "File Manager And File Manager Pro (Multiple Versions) - Directory Traversal", and its fields read all versions up to and including 7.2.1, with 7.2.2 patched. The vendor's download article gives the two editions separate update instructions.

Not by that alone. CVE-2026-19708 lists from version 7.2.2 up to and including 8.0.4, with 8.0.5 patched, and CVE-2026-85081 lists all versions up to and including 8.0.4. Every affected range in the history on this page counts, as well as the update guidance at the top of the history.

The listing marks Shortcode as a Pro feature. The plugin's help text says allowed_roles set to * "will allow all roles to access file manager on front end", or it can name roles such as editor and author; the vendor's Shortcodes page gives administrator as the default.

The listing describes Backup/Restore as covering "themes files, plugins files,uploads folder and db data on server". The plugin's own backup options are "Database Backup" and "Files Backup", with "Plugins", "Themes", "Uploads" and "Others (Any other directories found inside wp-content)".

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to 15 of the 16 records listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.