Recently registered widget Security & Risk Analysis

wordpress.org/plugins/recently-registered-widget

List of recently registered users

10 active installs v1.1 PHP + WP 3.4+ Updated Apr 16, 2015
latestrecentrecentlyregisteredregistred
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Recently registered widget Safe to Use in 2026?

Generally Safe

Score 85/100

Recently registered widget 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 "recently-registered-widget" plugin v1.1 presents a seemingly low-risk profile based on the static analysis and vulnerability history provided. The absence of identified entry points like AJAX handlers, REST API routes, shortcodes, and cron events, as well as the lack of dangerous functions and external HTTP requests, suggests a limited attack surface. Furthermore, no known vulnerabilities (CVEs) have been recorded for this plugin. This indicates a generally good security posture regarding common exploit vectors.

However, several areas raise concerns. The presence of SQL queries without prepared statements is a significant risk, as it can lead to SQL injection vulnerabilities if the data is not properly sanitized before being used in queries. The extremely low percentage of properly escaped output (7%) is also alarming. This indicates a high likelihood of Cross-Site Scripting (XSS) vulnerabilities, allowing attackers to inject malicious scripts into the website.

The lack of nonce checks and capability checks across the analyzed code is also a weakness, as these are fundamental security mechanisms in WordPress for preventing CSRF attacks and ensuring authorized access. While the taint analysis shows no critical or high severity flows, the data preparation and output handling practices are insufficient to reliably prevent common web vulnerabilities. In conclusion, while the plugin has avoided past public vulnerabilities and has a small attack surface, the identified code quality issues related to SQL queries and output escaping, along with missing authorization checks, represent tangible security risks that need to be addressed.

Key Concerns

  • SQL queries without prepared statements
  • Low percentage of properly escaped output (XSS risk)
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Recently registered widget Security Vulnerabilities

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

Recently registered widget Code Analysis

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

SQL Query Safety

0% prepared2 total queries

Output Escaping

7% escaped55 total outputs
Attack Surface

Recently registered widget Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwidgets_initrecently-registered-widget.php:12
Maintenance & Trust

Recently registered widget Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedApr 16, 2015
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Recently registered widget Developer Profile

Tomek

10 plugins · 220 total installs

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

How We Detect Recently registered widget

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/recently-registered-widget/lang

HTML / DOM Fingerprints

CSS Classes
widget_featured_entries
Data Attributes
id_base:recently-registered-widget
Shortcode Output
<center>They registered recently:</center><br>
FAQ

Frequently Asked Questions about Recently registered widget