Widget Content Blocks Security & Risk Analysis

wordpress.org/plugins/wysiwyg-widgets

Edit widget content using the default WordPress visual editor and media uploading functionality. Create widgets like you would create posts or pages.

10K active installs v2.3.11 PHP 7.4+ WP 4.1+ Updated Feb 27, 2026
rich-textvisual-editorwidgetwidgetswysiwyg
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Widget Content Blocks Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 1mo ago
Risk Assessment

The "wysiwyg-widgets" plugin version 2.3.11 demonstrates a strong security posture based on the provided static analysis. There are no identified attack vectors such as AJAX handlers, REST API routes, shortcodes, or cron events exposed without authentication. The code also avoids dangerous functions, file operations, and external HTTP requests. SQL queries are entirely secured using prepared statements, and there are no identified taint flows, indicating robust sanitization practices within the analyzed code.

Despite these strengths, a notable concern is the output escaping. While the majority of outputs (73%) are properly escaped, the remaining 27% are not, which could potentially lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is involved in these unescaped outputs. The absence of nonce checks on any entry points, while seemingly less critical given the limited attack surface, is a missed opportunity for an additional layer of security.

The plugin's vulnerability history is clean, with zero known CVEs and no recorded vulnerabilities. This suggests a commitment to security by the developers or a lack of historical exploitable issues. Overall, "wysiwyg-widgets" appears to be a secure plugin with excellent development practices, but the unescaped output presents a minor but addressable risk.

Key Concerns

  • Unescaped output identified
Vulnerabilities
None known

Widget Content Blocks Security Vulnerabilities

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

Widget Content Blocks Code Analysis

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

Output Escaping

73% escaped22 total outputs
Attack Surface

Widget Content Blocks Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 12
actionadd_meta_boxesincludes\class-admin.php:6
actionplugins_loadedincludes\plugin.php:9
actionwidgets_initincludes\plugin.php:19
actioninitincludes\plugin.php:49
filterww_contentincludes\plugin.php:52
filterww_contentincludes\plugin.php:53
filterww_contentincludes\plugin.php:54
filterww_contentincludes\plugin.php:55
filterww_contentincludes\plugin.php:56
filterww_contentincludes\plugin.php:57
filterww_contentincludes\plugin.php:58
filterww_contentincludes\plugin.php:59
Maintenance & Trust

Widget Content Blocks Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 27, 2026
PHP min version7.4
Downloads335K

Community Trust

Rating96/100
Number of ratings60
Active installs10K
Developer Profile

Widget Content Blocks Developer Profile

Danny van Kooten

9 plugins · 1.1M total installs

77
trust score
Avg Security Score
97/100
Avg Patch Time
655 days
View full developer profile
Detection Fingerprints

How We Detect Widget Content Blocks

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wysiwyg-widgets/

HTML / DOM Fingerprints

CSS Classes
ul-square
FAQ

Frequently Asked Questions about Widget Content Blocks