Skip to content

Product

wordpress simple-file-list vulnerabilities

21 published CVES affecting wordpress simple-file-list, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
21
Critical
2
High
10
Medium
9
Low
0
Unscored
0
CISA KEV
0

Latest wordpress simple-file-list CVEs

Newest publication first

  1. MediumCVSS 6.5 EPSS 0.47%

    The Simple File List plugin for WordPress is vulnerable to unauthorized file operations due to a missing authorization check on the 'frontmanage' shortcode attribute in all versions up to, and including, 6.3.7. This makes it possible for authenticated attackers, with contributor-...

  2. CriticalCVSS 9.8 EPSS 59.0% Framework module Public exploit Scanner template

    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 exe...

  3. MediumCVSS 4.8 EPSS 0.44%

    The Simple File List WordPress plugin before 6.0.10 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multis...

  4. MediumCVSS 4.8 EPSS 0.60%

    The Simple File List WordPress plugin before 4.4.12 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multis...

  5. HighCVSS 7.5 EPSS 17.5% Scanner template

    The Simple File List WordPress plugin is vulnerable to Arbitrary File Download via the eeFile parameter found in the ~/includes/ee-downloader.php file due to missing controls which makes it possible unauthenticated attackers to supply a path to a file that will subsequently be do...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.