Post Views for Jetpack Security & Risk Analysis

wordpress.org/plugins/post-views-for-jetpack

Display the number of views for each one of your posts, as recorded by Jetpack Stats.

1K active installs v1.5.0 PHP 5.6+ WP 6.0+ Updated Apr 25, 2025
jetpackpost-viewsstatsviews
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Post Views for Jetpack Safe to Use in 2026?

Generally Safe

Score 92/100

Post Views for Jetpack has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The plugin "post-views-for-jetpack" v1.5.0 demonstrates a generally strong security posture based on the provided static analysis. The absence of dangerous functions, external HTTP requests, and file operations is positive. Furthermore, all SQL queries are properly prepared, and the attack surface is minimal, with no unprotected entry points. However, there are areas for improvement. A significant concern is the lack of nonce and capability checks across all entry points, including the single shortcode. This leaves the plugin vulnerable to potential CSRF attacks and unauthorized actions if the shortcode's functionality can be exploited. While the current output escaping is at 75%, the remaining 25% could still lead to XSS vulnerabilities if user-supplied data is being outputted without proper sanitization.

The vulnerability history is a significant strength, showing no recorded CVEs. This suggests a history of stable and secure development or a lack of past exploitation. However, relying solely on this history can be misleading; the absence of past vulnerabilities does not guarantee future security, especially when critical security controls like nonce and capability checks are missing. In conclusion, the plugin is well-built in many areas, particularly regarding data handling and SQL security. The primary weakness lies in the insufficient input validation and authorization checks at its entry points, which represents a tangible risk despite a clean vulnerability history.

Key Concerns

  • No nonce checks on entry points
  • No capability checks on entry points
  • Unescaped output (25% of outputs)
Vulnerabilities
None known

Post Views for Jetpack Security Vulnerabilities

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

Post Views for Jetpack Release Timeline

v1.5.0Current
v1.4.0
v1.3.0
v1.2.0
v1.1.0
Code Analysis
Analyzed Mar 16, 2026

Post Views for Jetpack Code Analysis

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

Output Escaping

75% escaped16 total outputs
Attack Surface

Post Views for Jetpack Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[jp_post_view] jp-post-views.php:69
WordPress Hooks 5
actionplugins_loadedjp-post-views.php:42
actionadmin_noticesjp-post-views.php:55
actionrest_api_initjp-post-views.php:65
actionadmin_noticesjp-post-views.php:72
actionwidgets_initwidgets.jp-post-views.php:24
Maintenance & Trust

Post Views for Jetpack Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedApr 25, 2025
PHP min version5.6
Downloads25K

Community Trust

Rating100/100
Number of ratings13
Active installs1K
Developer Profile

Post Views for Jetpack Developer Profile

Jeremy Herve

11 plugins · 2K total installs

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

How We Detect Post Views for Jetpack

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

Asset Fingerprints

Version Parameters
post-views-for-jetpack/jp-post-views.php?ver=

HTML / DOM Fingerprints

REST Endpoints
/wp-json/wp/v2/posts?_fields=views
Shortcode Output
no views%s view%s views
FAQ

Frequently Asked Questions about Post Views for Jetpack