Pretty file list Security & Risk Analysis

wordpress.org/plugins/pretty-file-lister

A plugin that lists files attached to the current post/page.

100 active installs v0.4 PHP + WP 3.0.0+ Updated Mar 19, 2012
docdownload-linkfile-listingpdfxls
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Pretty file list Safe to Use in 2026?

Generally Safe

Score 85/100

Pretty file list has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 14yr ago
Risk Assessment

The "pretty-file-lister" v0.4 plugin exhibits a generally good security posture with a limited attack surface. The absence of known CVEs and a clean vulnerability history are positive indicators. However, the static analysis reveals significant concerns regarding output sanitization. With 100% of identified outputs not being properly escaped, this presents a substantial risk of cross-site scripting (XSS) vulnerabilities. While the plugin has capability checks, the lack of nonce checks on its single shortcode, which is the only entry point, leaves it susceptible to CSRF attacks if user-initiated actions are performed via this shortcode without proper validation.

The taint analysis indicates one flow with unsanitized paths, which, although not classified as critical or high severity, warrants investigation. This, combined with the unescaped outputs, suggests that user-supplied data could potentially be manipulated to execute malicious scripts or lead to unintended file access, even if not immediately apparent as a critical flaw. The plugin's strengths lie in its limited attack surface and use of prepared statements for SQL. Nevertheless, the identified weaknesses in output escaping and potential CSRF vectors are significant and require attention.

Key Concerns

  • Unescaped output found
  • Missing nonce check on shortcode
  • Taint flow with unsanitized paths
Vulnerabilities
None known

Pretty file list Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

Pretty file list Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
3
0 escaped
Nonce Checks
0
Capability Checks
2
File Operations
0
External Requests
0
Bundled Libraries
1

Bundled Libraries

TinyMCE

Output Escaping

0% escaped3 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

2 flows1 with unsanitized paths
srf_prettylist_settings (PrettyFileList.php:247)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Pretty file list Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[prettyfilelist] PrettyFileList.php:23
WordPress Hooks 7
actioninitPrettyFileList.php:43
actioninitPrettyFileList.php:45
actionadmin_menuPrettyFileList.php:50
filterattachment_fields_to_savePrettyFileList.php:52
actioninitPrettyFileList.php:54
filtermce_external_pluginsPrettyFileList.php:331
filtermce_buttonsPrettyFileList.php:332
Maintenance & Trust

Pretty file list Maintenance & Trust

Maintenance Signals

WordPress version tested3.3.2
Last updatedMar 19, 2012
PHP min version
Downloads8K

Community Trust

Rating100/100
Number of ratings1
Active installs100
Developer Profile

Pretty file list Developer Profile

smartredfox

1 plugin · 100 total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Pretty file list

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/pretty-file-lister/styles/prettylinks.css
Script Paths
/wp-content/plugins/pretty-file-lister/js/style_previewer.js

HTML / DOM Fingerprints

CSS Classes
prettyFileListprettylink
JS Globals
prettylistScriptParams
Shortcode Output
<a class="prettylinkprettyFileList
FAQ

Frequently Asked Questions about Pretty file list