mzz-stat Security & Risk Analysis

wordpress.org/plugins/mzz-stat

Shows the WP site administrator how many visits per page per day to their WP site.

100 active installs v20170304.1423 PHP + WP 4.4+ Updated Mar 5, 2017
hit-counterpage-viewsstatisticsstatsvisits-per-page-per-day
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is mzz-stat Safe to Use in 2026?

Generally Safe

Score 85/100

mzz-stat 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 "mzz-stat" plugin, version v20170304.1423, presents a mixed security posture. While the attack surface appears to be zero and there are no recorded CVEs or vulnerabilities, the static analysis reveals significant concerns within the codebase itself. The complete absence of prepared statements for all SQL queries and the lack of any output escaping are critical weaknesses that could lead to severe security issues like SQL injection and cross-site scripting (XSS) if the plugin were to interact with user-supplied data, even without obvious entry points exposed in the static analysis. The taint analysis also highlights two flows with unsanitized paths, indicating potential vulnerabilities that were not immediately apparent from the attack surface metrics.

Despite the clean vulnerability history, the internal code quality suggests a high potential for latent vulnerabilities. The lack of proper SQL sanitization and output escaping are fundamental security practices that are entirely missing. Therefore, while the plugin may appear secure on the surface due to a small attack surface and no historical CVEs, the underlying code is inherently risky and susceptible to exploitation if any data handling occurs. It is strongly recommended that this plugin undergo thorough code review and remediation for the identified SQL and output escaping issues before it is considered secure for production use.

Key Concerns

  • SQL queries without prepared statements
  • Output escaping is not implemented
  • Taint flows with unsanitized paths
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

mzz-stat Security Vulnerabilities

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

mzz-stat Release Timeline

v20170304.1423Current
v20160503.2046
v20160320.2203
v20151230.2238
Code Analysis
Analyzed Mar 16, 2026

mzz-stat Code Analysis

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

SQL Query Safety

0% prepared5 total queries

Output Escaping

0% escaped2 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
mzz_include_mzzstat (mzz-stat.php:92)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

mzz-stat Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionwp_footermzz-stat.php:90
actionadmin_menumzz-stat.php:143
Maintenance & Trust

mzz-stat Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.33
Last updatedMar 5, 2017
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs100
Developer Profile

mzz-stat Developer Profile

mjassen (mjjojo)

1 plugin · 100 total installs

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

How We Detect mzz-stat

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

Asset Fingerprints

HTML / DOM Fingerprints

HTML Comments
<!-- Utf-8 test -- two Utf-8 Chinese characters should appear at the beginning of this line. -->
FAQ

Frequently Asked Questions about mzz-stat