MC Visitor Tally Security & Risk Analysis

wordpress.org/plugins/mc-visitor-tally

Displays unique daily visits. Web page tables. Dashboard widget with monthly comparisons.

100 active installs v2.8.3 PHP 7.0+ WP 4.7+ Updated Nov 25, 2025
hit-countertraffic-countertraffic-statsvisitor-countervisitor-stats
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is MC Visitor Tally Safe to Use in 2026?

Generally Safe

Score 100/100

MC Visitor Tally has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 4mo ago
Risk Assessment

The mc-visitor-tally plugin v2.8.3 presents a mixed security posture. On the positive side, the plugin has no recorded vulnerabilities or CVEs, suggesting a history of responsible development or a lack of past exploitation. The static analysis also shows a low attack surface with no unprotected entry points, no dangerous functions, no file operations, and no external HTTP requests, which are all strong security indicators. However, significant concerns arise from the code analysis. The extremely low percentage of properly escaped output (4%) indicates a high risk of cross-site scripting (XSS) vulnerabilities. The single critical taint flow with unsanitized paths further amplifies this risk, suggesting that user-supplied data could be processed in an unsafe manner. While the majority of SQL queries use prepared statements, the presence of any raw SQL or unsanitized input in critical flows remains a concern. The absence of nonce and capability checks, while not directly flagged as problematic with the current limited attack surface, could become a significant weakness if new entry points are introduced or existing ones are modified without proper security controls.

Key Concerns

  • Low percentage of properly escaped output
  • Critical taint flow with unsanitized paths
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

MC Visitor Tally Security Vulnerabilities

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

MC Visitor Tally Code Analysis

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

SQL Query Safety

90% prepared21 total queries

Output Escaping

4% escaped54 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<mc-visitor-tally> (mc-visitor-tally.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

MC Visitor Tally Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[mcvt-visitor-tally] inc\mc6397vt_shortcode.php:5
WordPress Hooks 6
actionwp_dashboard_setupinc\mc6397vt_dashboard-widget.php:3
actionadmin_menuinc\mc6397vt_settings.php:7
actionadmin_initinc\mc6397vt_settings.php:8
actionadmin_initinc\mc6397vt_settings.php:9
actionwidgets_initinc\mc6397vt_widget.php:102
actionwp_headmc-visitor-tally.php:71
Maintenance & Trust

MC Visitor Tally Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedNov 25, 2025
PHP min version7.0
Downloads5K

Community Trust

Rating0/100
Number of ratings0
Active installs100
Developer Profile

MC Visitor Tally Developer Profile

Mike Hickcox

6 plugins · 240 total installs

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

How We Detect MC Visitor Tally

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
[mc6397vt-display-stats]
FAQ

Frequently Asked Questions about MC Visitor Tally