Specific Files Security & Risk Analysis

wordpress.org/plugins/specific-files-for-posts-and-pages

This plugin allows you to include CSS or JS files in specific posts and pages.

10 active installs v1.3.2 PHP + WP 3.0.0+ Updated Jul 13, 2014
cssjavascriptjspagestylesheet
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Specific Files Safe to Use in 2026?

Generally Safe

Score 85/100

Specific Files has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 12yr ago
Risk Assessment

The 'specific-files-for-posts-and-pages' plugin version 1.3.2 exhibits a mixed security posture. On the positive side, the plugin does not have any known historical vulnerabilities (CVEs) and utilizes prepared statements for all its SQL queries, which is a significant security strength. It also incorporates nonce and capability checks, indicating some effort towards securing its functionalities. However, several concerns arise from the static analysis. The plugin has a small attack surface of two AJAX handlers, both of which lack authentication checks, presenting a direct entry point for attackers. Furthermore, the taint analysis revealed two flows with unsanitized paths, although these did not escalate to critical or high severity in this analysis, they still represent potential risks if exploited in conjunction with other vulnerabilities. The relatively low percentage of properly escaped output (24%) also suggests a risk of cross-site scripting (XSS) vulnerabilities, especially since file operations are present in the code.

Key Concerns

  • Unprotected AJAX handlers
  • Flows with unsanitized paths
  • Low percentage of properly escaped output
Vulnerabilities
None known

Specific Files Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Specific Files Release Timeline

v1.3.1
v1.3
Code Analysis
Analyzed Mar 16, 2026

Specific Files Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
26
8 escaped
Nonce Checks
1
Capability Checks
4
File Operations
5
External Requests
0
Bundled Libraries
0

Output Escaping

24% escaped34 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

4 flows2 with unsanitized paths
wp_ajax_specific_delete_css_file (specific-files.php:370)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
2 unprotected

Specific Files Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_specific_delete_css_filespecific-files.php:148
authwp_ajax_specific_delete_js_filespecific-files.php:149
WordPress Hooks 5
actioninitspecific-files.php:143
actionadd_meta_boxesspecific-files.php:144
actionsave_postspecific-files.php:145
actionwp_headspecific-files.php:146
actionadmin_menuspecific-files.php:147
Maintenance & Trust

Specific Files Maintenance & Trust

Maintenance Signals

WordPress version tested3.9.40
Last updatedJul 13, 2014
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Specific Files Developer Profile

dwieeb

1 plugin · 10 total installs

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

How We Detect Specific Files

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/specific-files-for-posts-and-pages/css/colorbox.css/wp-content/plugins/specific-files-for-posts-and-pages/js/jquery.colorbox-min.js
Script Paths
/wp-content/plugins/specific-files-for-posts-and-pages/js/jquery.colorbox-min.js
Version Parameters
specific-files-for-posts-and-pages/css/colorbox.css?ver=specific-files-for-posts-and-pages/js/jquery.colorbox-min.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Specific Files