Page View Security & Risk Analysis

wordpress.org/plugins/popular-post

This plugin makes the list of the most popular 10 posts which you can see in sidebar just by activating it.

20 active installs v1.0 PHP + WP 3.0.1+ Updated May 24, 2016
most-viewed-postspopular-10-postspopular-posts
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Page View Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 9yr ago
Risk Assessment

The "popular-post" plugin version 1.0 exhibits a strong security posture based on the provided static analysis. There are no identified entry points like AJAX handlers, REST API routes, or shortcodes, which significantly limits the potential attack surface. Furthermore, the code signals indicate a lack of dangerous functions and a commitment to using prepared statements for all SQL queries. The absence of file operations and external HTTP requests also contributes to a more secure design. The vulnerability history being completely clean further reinforces this positive assessment, suggesting a well-maintained and secure plugin.

Despite the overall positive findings, there is one notable concern: 100% of the identified output is not properly escaped. This represents a potential risk of Cross-Site Scripting (XSS) vulnerabilities if user-controlled data is directly outputted into the HTML without sanitization. While the attack surface is currently zero, a future expansion of features or an introduction of new data sources could expose this weakness if not addressed. The lack of explicit nonce and capability checks also means that any future introduction of entry points would require careful security considerations to prevent unauthorized actions.

In conclusion, "popular-post" v1.0 appears to be a secure plugin with a minimal attack surface and good coding practices regarding SQL. However, the unescaped output is a critical flaw that needs immediate attention to prevent potential XSS vulnerabilities. The clean vulnerability history is a testament to its current security, but proactive measures for output sanitization are essential for maintaining this status.

Key Concerns

  • Unescaped output detected
Vulnerabilities
None known

Page View Security Vulnerabilities

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

Page View Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

Page View Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwp_headindex.php:33
Maintenance & Trust

Page View Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedMay 24, 2016
PHP min version
Downloads4K

Community Trust

Rating0/100
Number of ratings0
Active installs20
Developer Profile

Page View Developer Profile

Nirmal Bhagwani

1 plugin · 20 total installs

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

How We Detect Page View

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
widgetwidget-title
Shortcode Output
<div id="Viewed" class="widget"><h3 class="widget-title">Most Viewed Page</h3><ul><li><a href=""></a></li></ul></div>
FAQ

Frequently Asked Questions about Page View