Widget Instance Security & Risk Analysis

wordpress.org/plugins/widget-instance

Display an active widget added to a sidebar within the editor or by using a shortcode, function or action.

500 active installs v0.9.4 PHP + WP 2.9.1+ Updated Jul 11, 2018
display-widgetwidgetwidget-instancewidgets
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Widget Instance Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 7yr ago
Risk Assessment

The "widget-instance" plugin v0.9.4 exhibits a mixed security posture. On the positive side, it demonstrates good practices by utilizing prepared statements for all SQL queries and shows no history of known vulnerabilities (CVEs), suggesting a generally stable codebase. The absence of file operations and external HTTP requests also reduces potential attack vectors.

However, significant concerns arise from the static analysis. A notable portion of the attack surface, specifically 2 out of 3 entry points (AJAX handlers), lacks authentication checks. Furthermore, none of the outputs are properly escaped, creating a high risk of Cross-Site Scripting (XSS) vulnerabilities. The presence of unprotected AJAX handlers combined with unescaped output presents a critical threat, as attackers could potentially inject malicious scripts through these entry points, leading to data theft or session hijacking.

The lack of taint analysis results is neutral, as it could mean no critical flows were found or the analysis was not comprehensive enough to detect them. The outdated bundled TinyMCE library is a minor concern but could potentially be exploited if vulnerabilities exist in that specific version. Overall, the plugin has a concerning weakness in input sanitization and access control for its AJAX endpoints, outweighing its strengths in SQL handling and vulnerability history.

Key Concerns

  • Unprotected AJAX handlers
  • No output escaping
  • Bundled outdated library: TinyMCE v1.0
Vulnerabilities
None known

Widget Instance Security Vulnerabilities

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

Widget Instance Code Analysis

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

Bundled Libraries

TinyMCE1.0

Output Escaping

0% escaped1 total outputs
Attack Surface
2 unprotected

Widget Instance Attack Surface

Entry Points3
Unprotected2

AJAX Handlers 2

authwp_ajax_getWidgetsAjax.php:6
noprivwp_ajax_getWidgetsAjax.php:7

Shortcodes 1

[widget_instance] Public.php:21
WordPress Hooks 7
actionadmin_initAdmin.php:6
filtertiny_mce_versionAdmin.php:13
filtermce_external_pluginsAdmin.php:14
filtermce_buttonsAdmin.php:15
actionadmin_enqueue_scriptsAdmin.php:17
actioninitPublic.php:11
actionwidget_instancePublic.php:12
Maintenance & Trust

Widget Instance Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedJul 11, 2018
PHP min version
Downloads13K

Community Trust

Rating68/100
Number of ratings9
Active installs500
Developer Profile

Widget Instance Developer Profile

Global

3 plugins · 520 total installs

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

How We Detect Widget Instance

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/widget-instance/tinymce.js
Script Paths
/wp-content/plugins/widget-instance/tinymce.js

HTML / DOM Fingerprints

JS Globals
widgetinstance
Shortcode Output
[widget_instance
FAQ

Frequently Asked Questions about Widget Instance