WP Deferred JavaScripts Security & Risk Analysis

wordpress.org/plugins/wp-deferred-javascripts

Defer the loading of all JavaScripts added with wp_enqueue_script(), using LABJS (an asynchronous javascript library).

900 active installs v2.0.5 PHP + WP 3.0+ Updated Sep 1, 2016
deferringjavascriptlabjsoptimizationperformance
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Deferred JavaScripts Safe to Use in 2026?

Generally Safe

Score 85/100

WP Deferred JavaScripts has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9yr ago
Risk Assessment

The 'wp-deferred-javascripts' plugin v2.0.5 exhibits a strong security posture based on the provided static analysis. It demonstrates excellent practices by having no detected dangerous functions, no SQL queries outside of prepared statements, no file operations, and no external HTTP requests. Furthermore, the complete absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the attack surface. Taint analysis also shows no critical or high-severity issues, and the plugin has no recorded vulnerability history, indicating a mature and secure development process for this version.

However, a key area for concern is the lack of nonce checks and capability checks across all potential entry points. While the attack surface is currently zero, any future expansion of functionality without implementing these crucial security measures could introduce significant risks. Additionally, the output escaping is not perfect, with 37% of outputs potentially unescaped, which could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is involved in these outputs. The absence of any recorded vulnerabilities is a positive sign, but the lack of built-in access controls remains a potential weakness.

Key Concerns

  • No nonce checks detected
  • No capability checks detected
  • Significant percentage of unescaped output
Vulnerabilities
None known

WP Deferred JavaScripts Security Vulnerabilities

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

WP Deferred JavaScripts Code Analysis

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

Output Escaping

63% escaped8 total outputs
Attack Surface

WP Deferred JavaScripts Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actionplugins_loadedinc\admin.php:17
actionadmin_initinc\admin.php:31
actionadmin_menuinc\admin.php:40
filterdo_not_deferinc\frontend.php:91
filterprint_scripts_arrayinc\frontend.php:109
filterscript_loader_srcinc\frontend.php:150
actionwp_footerinc\frontend.php:172
filterplugin_row_metawp-deferred-javascripts.php:30
Maintenance & Trust

WP Deferred JavaScripts Maintenance & Trust

Maintenance Signals

WordPress version tested4.6.30
Last updatedSep 1, 2016
PHP min version
Downloads159K

Community Trust

Rating64/100
Number of ratings35
Active installs900
Developer Profile

WP Deferred JavaScripts Developer Profile

Willy Bahuaud

8 plugins · 9K total installs

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

How We Detect WP Deferred JavaScripts

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-deferred-javascripts/assets/js/lab.min.js
Script Paths
/wp-content/plugins/wp-deferred-javascripts/assets/js/lab.min.js
Version Parameters
wp-deferred-javascripts/assets/js/lab.min.js?ver=

HTML / DOM Fingerprints

JS Globals
WDJS_PLUGIN_URLWDJS_VERSION
FAQ

Frequently Asked Questions about WP Deferred JavaScripts