Plugin Stats View Security & Risk Analysis

wordpress.org/plugins/plugin-stats-view

The stats of plugin is displayed by block or shortcode.

10 active installs v3.14 PHP 8.0+ WP 6.6+ Updated Mar 29, 2026
blockpluginsstats
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Plugin Stats View Safe to Use in 2026?

Generally Safe

Score 100/100

Plugin Stats View 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 plugin "plugin-stats-view" v3.14 presents a generally positive security posture based on the provided static analysis and vulnerability history. The absence of known vulnerabilities (CVEs) and the thorough nature of the code analysis, which identified no critical or high severity taint flows, are significant strengths. Furthermore, the plugin exhibits good practices by having no external HTTP requests, no file operations, and no shortcodes or cron events to exploit. This indicates a well-contained and potentially robust plugin.

However, there are notable areas of concern. The most significant is the single SQL query, which is not utilizing prepared statements. This presents a direct risk of SQL injection, a common and severe vulnerability. Additionally, the complete lack of nonce checks and capability checks is a substantial security weakness. While the attack surface for AJAX and REST API routes is reported as zero, this might be a misleading statistic if these entry points are not properly secured or if the analysis missed them. The low percentage of properly escaped output also raises a flag, potentially indicating a risk of Cross-Site Scripting (XSS) vulnerabilities, especially if sensitive data is being displayed.

In conclusion, while the plugin benefits from a clean vulnerability history and limited attack surface, the identified risks related to raw SQL queries and the complete absence of nonces and capability checks are serious and require immediate attention. The low output escaping rate also needs further investigation. It is recommended to address these specific issues to enhance the overall security of the plugin.

Key Concerns

  • SQL query not using prepared statements
  • No nonce checks implemented
  • No capability checks implemented
  • Low output escaping rate (18% unescaped)
Vulnerabilities
None known

Plugin Stats View Security Vulnerabilities

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

Plugin Stats View Release Timeline

v3.14Current
v3.13
v3.12
v3.11
v3.10
v3.09
v3.08
v3.07
v3.06
v3.05
v3.04
v3.03
v3.02
v3.01
v3.00
v2.28
v2.27
v2.26
v2.25
v2.24
Code Analysis
Analyzed Mar 17, 2026

Plugin Stats View Code Analysis

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

SQL Query Safety

0% prepared1 total queries

Output Escaping

82% escaped170 total outputs
Attack Surface

Plugin Stats View Attack Surface

Entry Points0
Unprotected0
Maintenance & Trust

Plugin Stats View Maintenance & Trust

Maintenance Signals

WordPress version tested7.0
Last updatedMar 29, 2026
PHP min version8.0
Downloads5K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Plugin Stats View Developer Profile

Katsushi Kawamori

54 plugins · 56K total installs

79
trust score
Avg Security Score
100/100
Avg Patch Time
178 days
View full developer profile
Detection Fingerprints

How We Detect Plugin Stats View

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/plugin-stats-view/js/psv-editor.js/wp-content/plugins/plugin-stats-view/css/psv-editor.css/wp-content/plugins/plugin-stats-view/js/psv-stats.js/wp-content/plugins/plugin-stats-view/css/psv-stats.css/wp-content/plugins/plugin-stats-view/js/psv-admin.js/wp-content/plugins/plugin-stats-view/css/psv-admin.css
Script Paths
/wp-content/plugins/plugin-stats-view/js/psv-editor.js/wp-content/plugins/plugin-stats-view/js/psv-stats.js/wp-content/plugins/plugin-stats-view/js/psv-admin.js
Version Parameters
plugin-stats-view/js/psv-editor.js?ver=plugin-stats-view/css/psv-editor.css?ver=plugin-stats-view/js/psv-stats.js?ver=plugin-stats-view/css/psv-stats.css?ver=plugin-stats-view/js/psv-admin.js?ver=plugin-stats-view/css/psv-admin.css?ver=

HTML / DOM Fingerprints

CSS Classes
psv-settings-wrappsv-stats-wrappsv-admin-wrappsv-editor-wrap
Data Attributes
data-psv-plugin-namedata-psv-versiondata-psv-stats-id
JS Globals
psv_settings_objectpsv_plugin_stats
REST Endpoints
/wp-json/plugin-stats-view/v1/settings
Shortcode Output
[plugin_stats_view][psv_stats]
FAQ

Frequently Asked Questions about Plugin Stats View