MCB – Stats Security & Risk Analysis

wordpress.org/plugins/mcb-stats

MCB Stats collects statistics of users who access to the front part of wordpress, MCB Stast is capable of collecting the total amount of time a user s …

10 active installs v1.0.0 PHP + WP 4+ Updated May 11, 2017
page-counterpage-visitpost-countertimetime-in-page
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is MCB – Stats Safe to Use in 2026?

Generally Safe

Score 85/100

MCB – Stats has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The "mcb-stats" v1.0.0 plugin exhibits a concerning security posture primarily due to its unprotected AJAX endpoints. With 7 AJAX handlers identified, all lacking proper authentication or authorization checks, this presents a significant attack surface. Furthermore, the taint analysis reveals 3 flows with unsanitized paths, including 2 of high severity, indicating potential for attackers to inject malicious data that could be executed or lead to unintended consequences within the plugin. The complete absence of nonce checks and capability checks exacerbates these risks, as there are no built-in mechanisms to verify user intent or permissions for these sensitive actions.

While the plugin has no recorded vulnerability history, which is a positive indicator of past code quality, it does not mitigate the immediate risks identified in the static and taint analysis. The use of SQL queries without prepared statements is another critical weakness, increasing the likelihood of SQL injection vulnerabilities. The bundled DataTables library, while not inherently a vulnerability, should be monitored for known issues in its specific version. Overall, the plugin's strengths lie in its lack of direct file operations and external HTTP requests, and a moderate rate of proper output escaping. However, the severe lack of input validation and authentication on its AJAX endpoints and the presence of high-severity taint flows are major security concerns that require immediate attention.

Key Concerns

  • Unprotected AJAX handlers
  • High severity taint flows
  • Raw SQL without prepared statements
  • Missing nonce checks
  • Missing capability checks
  • Flows with unsanitized paths
  • Bundled outdated library (DataTables v1.10.13)
Vulnerabilities
None known

MCB – Stats Security Vulnerabilities

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

MCB – Stats Code Analysis

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

Bundled Libraries

DataTables1.10.13

SQL Query Safety

0% prepared7 total queries

Output Escaping

65% escaped37 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

4 flows3 with unsanitized paths
save_mcb_stats_sttings (mcb-stats.php:567)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
7 unprotected

MCB – Stats Attack Surface

Entry Points7
Unprotected7

AJAX Handlers 7

authwp_ajax_stats_ajax_mcbmcb-stats.php:539
noprivwp_ajax_stats_ajax_mcbmcb-stats.php:540
authwp_ajax_stats_ajax_mcb_update_timemcb-stats.php:555
noprivwp_ajax_stats_ajax_mcb_update_timemcb-stats.php:556
authwp_ajax_reset_data_mcb_statsmcb-stats.php:565
authwp_ajax_save_mcb_stats_sttingsmcb-stats.php:583
authwp_ajax_get_data_mcb_statsmcb-stats.php:632
WordPress Hooks 5
actionwp_headmcb-stats.php:191
actionwp_loginmcb-stats.php:224
actionwp_logoutmcb-stats.php:257
actionadmin_menumcb-stats.php:263
filterplugin_row_metamcb-stats.php:272
Maintenance & Trust

MCB – Stats Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.32
Last updatedMay 11, 2017
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

MCB – Stats Developer Profile

mariusromanus

1 plugin · 10 total installs

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

How We Detect MCB – Stats

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/mcb-stats/js/mcb_stats.js/wp-content/plugins/mcb-stats/js/mcb_stats_count.js
Script Paths
/wp-content/plugins/mcb-stats/js/mcb_stats.js/wp-content/plugins/mcb-stats/js/mcb_stats_count.js

HTML / DOM Fingerprints

JS Globals
window.location.originwindow.location.protocolwindow.location.hostnamewindow.location.portwindow.location.pathnamewindow.Worker+1 more
REST Endpoints
/wp-admin/admin-ajax.php
FAQ

Frequently Asked Questions about MCB – Stats