
WP Server Health Stats Security & Risk Analysis
wordpress.org/plugins/wp-server-statsMonitor your WP site the right way with most important stats like Database, PHP details, PHP Memory, RAM Usage, CPU load, Server Uptime & more.
Is WP Server Health Stats Safe to Use in 2026?
Generally Safe
Score 87/100WP Server Health Stats has a strong security track record. Known vulnerabilities have been patched promptly.
The 'wp-server-stats' plugin v1.8.0 presents a mixed security posture. On the positive side, the code analysis indicates good practices in several areas. All identified AJAX entry points have authentication checks, there are no vulnerable REST API routes or shortcodes, and SQL queries are exclusively handled using prepared statements. Furthermore, a very high percentage of output is properly escaped, and there are no file operations or instances of unsanitized paths in taint flows. This suggests a reasonable effort has been made to prevent common web vulnerabilities.
However, significant concerns arise from the presence of the 'shell_exec' dangerous function and the plugin's vulnerability history. The 'shell_exec' function, if not handled with extreme care, can be a vector for remote code execution. While no critical taint flows were identified in the current analysis, the historical presence of critical vulnerabilities, including embedded malicious code and cross-site scripting, coupled with a recent critical vulnerability recorded on 2024-06-24, indicates a recurring pattern of security weaknesses that have required significant attention. The existence of three known CVEs, even if currently patched, suggests past issues that could potentially resurface or be discovered in new forms.
In conclusion, while v1.8.0 shows improvements in specific secure coding practices, the historical context of critical vulnerabilities and the presence of 'shell_exec' warrant caution. The plugin has a history of being targeted with severe issues. Users should remain vigilant and ensure the plugin is always updated to the absolute latest version, as past vulnerabilities have been critical in nature. The 'shell_exec' function requires thorough auditing to ensure it is not exploitable.
Key Concerns
- Dangerous function: shell_exec
- Total known CVEs: 3 (1 critical, 2 medium)
- Last vulnerability: 2024-06-24 (critical)
WP Server Health Stats Security Vulnerabilities
CVEs by Year
Severity Breakdown
3 total CVEs
Several WordPress.org Plugins <= Various Versions - Injected Backdoor
WP Server Health Stats <= 1.7.3 - Cross-Site Request Forgery
WP Server Health Stats <= 1.6.10 - Authenticated (Administrator+) Stored Cross-Site Scripting
WP Server Health Stats Code Analysis
Dangerous Functions Found
SQL Query Safety
Output Escaping
Data Flow Analysis
WP Server Health Stats Attack Surface
AJAX Handlers 4
WordPress Hooks 9
Maintenance & Trust
WP Server Health Stats Maintenance & Trust
Maintenance Signals
Community Trust
WP Server Health Stats Alternatives
atec System Info
atec-system-info
atec System Info (Operating system, server, memory, PHP and database details)
Web Server Information
wpheka-web-server-information
Web Server Information plugin will give you detailed information about your hosting server's configuration and installed modules.
Version Info – Server Health Monitor, PHP & MySQL Version Display, Environment Indicators
version-info
The #1 technical dashboard for WordPress professionals. Display PHP, MySQL, WP & server versions anywhere in admin. Monitor CPU, RAM, DB size & …
Server Info for Debugging
server-info-for-debugging
Displays server stats and WordPress system information for debugging purposes.
Diagnosis
diagnosis
Adds pages to the Dashboard menu with technical details about PHP, MySQL and other server details an administrator might need.
WP Server Health Stats Developer Profile
2 plugins · 30K total installs
How We Detect WP Server Health Stats
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/wp-server-stats/css/wpss-admin-styles.css/wp-content/plugins/wp-server-stats/css/wpss-dashboard-widget-style.css/wp-content/plugins/wp-server-stats/css/wpss-footer-style.css/wp-content/plugins/wp-server-stats/js/wpss-admin-script.js/wp-content/plugins/wp-server-stats/js/wpss-dashboard-widget-script.js/wp-content/plugins/wp-server-stats/js/wpss-footer-script.js/wp-content/plugins/wp-server-stats/js/wpss-modal.js/wp-content/plugins/wp-server-stats/js/wpss-admin-script.js/wp-content/plugins/wp-server-stats/js/wpss-dashboard-widget-script.js/wp-content/plugins/wp-server-stats/js/wpss-footer-script.js/wp-content/plugins/wp-server-stats/js/wpss-modal.jswp-server-stats/css/wpss-admin-styles.css?ver=wp-server-stats/css/wpss-dashboard-widget-style.css?ver=wp-server-stats/css/wpss-footer-style.css?ver=wp-server-stats/js/wpss-admin-script.js?ver=wp-server-stats/js/wpss-dashboard-widget-script.js?ver=wp-server-stats/js/wpss-footer-script.js?ver=wp-server-stats/js/wpss-modal.js?ver=HTML / DOM Fingerprints
wpss-admin-wrapperwpss-dashboard-wrapperwpss-footer-wrapperwpss-advanced-info-tablewpss-server-load-chart<!-- This file should NEVER be accessed directly. --><!-- WP Server Stats Settings Page --><!-- WP Server Stats Dashboard Widget --><!-- WP Server Stats Admin Footer -->+2 moredata-wpss-noncedata-wpss-actionwpss_admin_datawpss_dashboard_datawpss_footer_datawpss_modal_data/wp-json/wp-server-stats/v1/settings/wp-json/wp-server-stats/v1/data[wp_server_stats_info][wp_server_stats_memory_usage][wp_server_stats_server_load]