The Hits Counter Security & Risk Analysis

wordpress.org/plugins/the-hits-counter

Checks and displays the number of hits for posts and pages

10 active installs v1.0 PHP + WP 2.1+ Updated Feb 10, 2026
counterhits
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is The Hits Counter Safe to Use in 2026?

Generally Safe

Score 100/100

The Hits Counter 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 'the-hits-counter' v1.0 exhibits a generally strong security posture based on the provided static analysis. The absence of dangerous functions, raw SQL queries, file operations, and external HTTP requests is commendable. Importantly, all SQL queries utilize prepared statements, which mitigates the risk of SQL injection. However, there are some areas of concern. The plugin has a relatively low number of outputs, but a significant portion (33%) are not properly escaped, posing a potential risk of cross-site scripting (XSS) vulnerabilities if user-supplied data is reflected directly in the output. Additionally, the complete lack of nonce checks and capability checks across all entry points, including the single shortcode, is a notable weakness. While the attack surface is currently small, these missing authorization mechanisms mean that an attacker could potentially leverage the shortcode's functionality without proper validation, leading to unintended actions or information disclosure. The plugin's vulnerability history is clean, with no recorded CVEs, which suggests a history of good security practices or a lack of significant past vulnerabilities being discovered. Overall, the plugin is built on a solid foundation but requires attention to output escaping and robust authorization checks to reach a more secure state.

Key Concerns

  • Missing nonce checks on entry points
  • Missing capability checks on entry points
  • Unescaped output detected
Vulnerabilities
None known

The Hits Counter Security Vulnerabilities

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

The Hits Counter Code Analysis

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

Output Escaping

67% escaped3 total outputs
Attack Surface

The Hits Counter Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[thc_hits_count] init.php:66
WordPress Hooks 3
actionwpinit.php:22
filterthc_display_countinit.php:77
filterthe_contentinit.php:89
Maintenance & Trust

The Hits Counter Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 10, 2026
PHP min version
Downloads8K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

The Hits Counter Developer Profile

Gagan Deep Singh

8 plugins · 65K total installs

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

How We Detect The Hits Counter

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
hits-counter
Shortcode Output
[thc_hits_count]
FAQ

Frequently Asked Questions about The Hits Counter