Duplicate Widget Security & Risk Analysis

wordpress.org/plugins/duplicate-widget

A widget that can act as a duplicate of another widget (for synchronized use in another sidebar)

1K active installs v1.0.2 PHP + WP 3.1+ Updated Nov 28, 2017
coffee2codeduplicatesidebarwidgetwidgets
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Duplicate Widget Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The "duplicate-widget" plugin v1.0.2 exhibits a strong security posture based on the provided static analysis and vulnerability history. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the plugin's attack surface. Furthermore, the code analysis reveals no dangerous functions, no file operations, and no external HTTP requests, which are common vectors for exploitation. The use of prepared statements for all SQL queries is a positive indicator of secure database interaction. The lack of any known CVEs, past or present, suggests a history of responsible development and patching. However, the output escaping rate of only 20% is a notable concern. This indicates that potentially a significant portion of the plugin's output is not properly sanitized, leaving it vulnerable to cross-site scripting (XSS) attacks if any user-supplied data is directly reflected in the output without adequate escaping. The absence of nonce checks and capability checks, while not directly flagged as an issue due to the limited attack surface, could become a risk if new entry points are introduced in future versions without proper authorization and integrity checks. Overall, the plugin is currently in a good security state, but the unescaped output represents a clear area for improvement to mitigate potential XSS vulnerabilities.

Key Concerns

  • Output escaping is significantly lacking (20%)
  • No nonce checks present
  • No capability checks present
Vulnerabilities
None known

Duplicate Widget Security Vulnerabilities

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

Duplicate Widget Release Timeline

v1.0.2Current
v1.0.1
v1.0
Code Analysis
Analyzed Mar 16, 2026

Duplicate Widget Code Analysis

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

Output Escaping

20% escaped5 total outputs
Attack Surface

Duplicate Widget Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionwidgets_initduplicate-widget.php:80
actionin_widget_formduplicate-widget.php:82
actionadmin_initduplicate-widget.php:84
actionload-widgets.phpduplicate-widget.php:86
actionadmin_enqueue_scriptsduplicate-widget.php:112
actionadmin_initduplicate-widget.php:114
Maintenance & Trust

Duplicate Widget Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedNov 28, 2017
PHP min version
Downloads28K

Community Trust

Rating86/100
Number of ratings12
Active installs1K
Developer Profile

Duplicate Widget Developer Profile

Scott Reilly

63 plugins · 92K total installs

71
trust score
Avg Security Score
88/100
Avg Patch Time
374 days
View full developer profile
Detection Fingerprints

How We Detect Duplicate Widget

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/duplicate-widget/js/admin.js
Script Paths
/wp-content/plugins/duplicate-widget/js/admin.js
Version Parameters
duplicate-widget/js/admin.js?ver=

HTML / DOM Fingerprints

Data Attributes
data-widget_to_duplicate
JS Globals
duplicate-widget
FAQ

Frequently Asked Questions about Duplicate Widget