Site Protection Security & Risk Analysis

wordpress.org/plugins/presslabs-site-protection

Site protection plugin for dev instances to avoid indexing by search engines. Doesn't allow access to the site without being logged-in.

10 active installs v1.3 PHP + WP 4.7+ Updated Dec 4, 2025
avoid-indexingloginpresslabssite-protectiontemplate
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Site Protection Safe to Use in 2026?

Generally Safe

Score 100/100

Site Protection has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 5mo ago
Risk Assessment

The plugin 'presslabs-site-protection' v1.3 exhibits a seemingly strong security posture based on the provided static analysis. It boasts zero identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in a completely closed attack surface with no unprotected entry points. The code also shows positive signs with no dangerous functions, no file operations, and no external HTTP requests. Importantly, all SQL queries, if any existed, would be using prepared statements, and there are no recorded vulnerabilities in its history, indicating a clean track record.

However, a significant concern arises from the lack of output escaping, with 100% of outputs being unescaped. This indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities, as data displayed to users might not be properly sanitized, allowing attackers to inject malicious scripts. Furthermore, the complete absence of nonce and capability checks, despite the potential for functionality to exist (even if not immediately apparent from the entry point analysis), suggests a potential lack of authorization and protection against CSRF attacks if any actions are performed. The lack of taint analysis flows is also unusual and could indicate either a very simple plugin or an incomplete analysis.

In conclusion, while the plugin appears to have a minimal attack surface and a clean vulnerability history, the unescaped output presents a critical and undeniable risk. The absence of nonce and capability checks also warrants caution. It's recommended to prioritize addressing the output escaping issue and investigate the implementation of authorization checks if any administrative or sensitive functions are present.

Key Concerns

  • 100% unescaped output
  • 0 capability checks
  • 0 nonce checks
Vulnerabilities
None known

Site Protection Security Vulnerabilities

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

Site Protection Release Timeline

v1.3Current
v1.2
v1.1
v1.0
Code Analysis
Analyzed Apr 16, 2026

Site Protection Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

Site Protection Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actiontemplate_redirectpresslabs-site-protection.php:11
actionplugins_loadedpresslabs-site-protection.php:28
Maintenance & Trust

Site Protection Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedDec 4, 2025
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Site Protection Developer Profile

Presslabs

6 plugins · 1K total installs

94
trust score
Avg Security Score
100/100
Avg Patch Time
25 days
View full developer profile
Detection Fingerprints

How We Detect Site Protection

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/presslabs-site-protection/languages

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Site Protection