Custom Recent Posts Widget Security & Risk Analysis

wordpress.org/plugins/custom-recent-posts-widget

A widget to show recent posts list based on categories or tags

1K active installs v2.1.1 PHP + WP 3.1+ Updated Nov 28, 2017
categoriescategoryrecent-poststagtags
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Custom Recent Posts Widget Safe to Use in 2026?

Generally Safe

Score 85/100

Custom Recent Posts 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 plugin 'custom-recent-posts-widget' v2.1.1 exhibits a generally strong security posture based on the provided static analysis. The absence of any identified attack surface entry points like AJAX handlers, REST API routes, or shortcodes, coupled with zero critical or high severity taint flows, is highly commendable. Furthermore, all SQL queries utilize prepared statements, and there are no file operations or external HTTP requests, all of which are excellent security practices. The plugin also has no known vulnerability history, indicating a history of secure development or prompt patching.

However, a significant concern arises from the very low percentage of properly escaped output (17%). This suggests a substantial risk of Cross-Site Scripting (XSS) vulnerabilities, as user-supplied or dynamic data is likely being rendered without adequate sanitization. While there are no direct indicators of XSS in the taint analysis, the sheer volume of unescaped output presents a broad attack vector. The complete lack of nonce checks and capability checks on the identified (zero) entry points, while seemingly benign given the lack of entry points, means that if any were to be introduced or if the static analysis missed something, there would be no built-in protection.

In conclusion, the plugin demonstrates a commitment to secure coding practices in many areas. The lack of known vulnerabilities and secure database interactions are significant strengths. The primary weakness, however, is the widespread issue with output escaping, which poses a considerable risk of XSS. This warrants immediate attention and remediation.

Key Concerns

  • Low output escaping percentage
Vulnerabilities
None known

Custom Recent Posts Widget Security Vulnerabilities

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

Custom Recent Posts Widget Code Analysis

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

Output Escaping

17% escaped46 total outputs
Attack Surface

Custom Recent Posts Widget Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionwidgets_initincludes\crpw-cat.php:128
actionwidgets_initincludes\crpw-tag.php:132
Maintenance & Trust

Custom Recent Posts Widget Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedNov 28, 2017
PHP min version
Downloads51K

Community Trust

Rating98/100
Number of ratings9
Active installs1K
Developer Profile

Custom Recent Posts Widget Developer Profile

Prasanna SP

6 plugins · 2K total installs

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

How We Detect Custom Recent Posts Widget

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/custom-recent-posts-widget/includes/css/crpw-style.css/wp-content/plugins/custom-recent-posts-widget/includes/js/crpw-script.js
Script Paths
/wp-content/plugins/custom-recent-posts-widget/includes/js/crpw-script.js
Version Parameters
custom-recent-posts-widget/includes/css/crpw-style.css?ver=custom-recent-posts-widget/includes/js/crpw-script.js?ver=

HTML / DOM Fingerprints

CSS Classes
crpw-category-widgetcrpw-tag-widget
FAQ

Frequently Asked Questions about Custom Recent Posts Widget