WP Site Monitor Security & Risk Analysis

wordpress.org/plugins/wp-site-monitor

Extends official WP REST API to provide extra endpoints to help manage sites remotely.

20 active installs v1.0.0 PHP 5.6+ WP 4.7+ Updated Feb 4, 2018
adminapiremote-administrationrestrest-api
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Site Monitor Safe to Use in 2026?

Generally Safe

Score 85/100

WP Site Monitor 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 "wp-site-monitor" v1.0.0 plugin exhibits a strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points suggests a minimal attack surface. Furthermore, the code signals indicate good development practices, with no dangerous functions, all SQL queries utilizing prepared statements, and all output properly escaped. The absence of file operations, external HTTP requests, and evident taint flows further contribute to its secure design. The plugin also implements capability checks, which is a positive security measure.

However, the complete lack of nonce checks (0) across all entry points, even though the attack surface is currently zero, represents a potential future risk. If functionality were to be added later that utilized AJAX or other forms of user interaction, the absence of nonce checks could expose the plugin to Cross-Site Request Forgery (CSRF) vulnerabilities. The vulnerability history being entirely clear is a positive indicator, suggesting the plugin has historically been maintained with security in mind or has not been a target for widespread exploitation. Overall, the current version of "wp-site-monitor" appears very secure due to its limited functionality and adherence to secure coding principles, but the lack of nonce checks warrants attention for future development.

Key Concerns

  • No nonce checks implemented
Vulnerabilities
None known

WP Site Monitor Security Vulnerabilities

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

WP Site Monitor Release Timeline

v1.0.0Current
v0.1.0
Code Analysis
Analyzed Mar 16, 2026

WP Site Monitor Code Analysis

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

Output Escaping

100% escaped18 total outputs
Attack Surface

WP Site Monitor Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_initsrc\class-wp-site-monitor.php:90
actionadmin_menusrc\class-wp-site-monitor.php:91
actionrest_api_initsrc\class-wp-site-monitor.php:97
Maintenance & Trust

WP Site Monitor Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedFeb 4, 2018
PHP min version5.6
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs20
Developer Profile

WP Site Monitor Developer Profile

bwibrew

1 plugin · 20 total installs

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

How We Detect WP Site Monitor

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-site-monitor/vendor/composer/installers/src/Composer/Installers

HTML / DOM Fingerprints

REST Endpoints
wp-site-monitor/v1/wp-versionwp-site-monitor/v1/plugins
FAQ

Frequently Asked Questions about WP Site Monitor