Custom CSS/JS Security & Risk Analysis

wordpress.org/plugins/custom-cssjs

Add custom javascripts and styles to pages and posts as well as your entire site.

80 active installs v1.0 PHP + WP 3.0+ Updated Sep 14, 2015
csscustomjavascriptjsstyle
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Custom CSS/JS Safe to Use in 2026?

Generally Safe

Score 85/100

Custom CSS/JS has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10yr ago
Risk Assessment

The "custom-cssjs" v1.0 plugin exhibits a generally positive security posture based on the provided static analysis. The absence of any known CVEs and a clean vulnerability history strongly suggests a history of responsible development and patching. The code analysis reveals a remarkably small attack surface with no identified AJAX handlers, REST API routes, shortcodes, or cron events that are exposed. Furthermore, the plugin demonstrates good practices with 100% of its SQL queries using prepared statements and the presence of nonce and capability checks. However, a significant concern arises from the low percentage (8%) of properly escaped outputs. This indicates a potential for cross-site scripting (XSS) vulnerabilities if user-supplied data is directly outputted without adequate sanitization, especially given the absence of any taint flow issues that would typically flag such problems. While the current taint analysis shows no critical or high-severity flows, the low output escaping rate remains a primary weakness. In conclusion, the plugin benefits from a minimal attack surface and good data handling for SQL, but the weak output escaping requires attention to mitigate potential XSS risks.

Key Concerns

  • Low percentage of properly escaped outputs
Vulnerabilities
None known

Custom CSS/JS Security Vulnerabilities

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

Custom CSS/JS Code Analysis

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

Output Escaping

8% escaped12 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
save_meta_box_data (custom-css-js.php:138)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Custom CSS/JS Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionadd_meta_boxescustom-css-js.php:37
actionsave_postcustom-css-js.php:38
actionadmin_menucustom-css-js.php:39
actionadmin_enqueue_scriptscustom-css-js.php:40
actionwp_print_footer_scriptscustom-css-js.php:43
actionwp_print_footer_scriptscustom-css-js.php:44
Maintenance & Trust

Custom CSS/JS Maintenance & Trust

Maintenance Signals

WordPress version tested4.3.34
Last updatedSep 14, 2015
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings1
Active installs80
Developer Profile

Custom CSS/JS Developer Profile

becauseinterwebs

1 plugin · 80 total installs

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

How We Detect Custom CSS/JS

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/custom-cssjs/style.css
Version Parameters
custom-cssjs/style.css?ver=1.0

HTML / DOM Fingerprints

CSS Classes
biw_textarea
Data Attributes
name="biw_custom_css"name="biw_custom_js"name="biw_custom_js_external"name="biw_meta_box_nonce_css"name="biw_meta_box_nonce_js"name="biw_meta_box_nonce_js_external"+3 more
FAQ

Frequently Asked Questions about Custom CSS/JS