Discourage Search Engines by URL Security & Risk Analysis

wordpress.org/plugins/discourage-search-engines-by-url

Allows you to discourage search engines by url to prevent you from forgetting to turn the setting off when transfering databases between development a …

80 active installs v0.2.1 PHP + WP 4.1+ Updated Jan 6, 2017
discourageenginesearchurlvisibility
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Discourage Search Engines by URL Safe to Use in 2026?

Generally Safe

Score 85/100

Discourage Search Engines by URL has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9yr ago
Risk Assessment

The "discourage-search-engines-by-url" plugin v0.2.1 exhibits a generally positive security posture based on the provided static analysis. The plugin has no known CVEs, a clean vulnerability history, and a notably absent attack surface with zero entry points (AJAX, REST API, shortcodes, cron events). The code also avoids dangerous functions, file operations, and external HTTP requests. Importantly, all SQL queries utilize prepared statements, which is a strong defense against SQL injection. However, a significant concern arises from the output escaping. With 5 total outputs analyzed, only 20% (1 output) are properly escaped. This indicates a potential for Cross-Site Scripting (XSS) vulnerabilities, as unsanitized data could be injected into the frontend and executed by users' browsers. The lack of nonce and capability checks, while not directly exploitable due to the zero attack surface, represents a missed opportunity for layered security that could become a liability if the attack surface expands in future versions. The absence of taint analysis flows is also noteworthy, suggesting either a lack of complex data handling or that the analysis tool did not identify any concerning data flows within the plugin's current scope. Overall, while the plugin demonstrates good practices in core areas like SQL and attack surface management, the poor output escaping is a critical weakness that needs immediate attention.

Key Concerns

  • Poor output escaping (20% escaped)
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

Discourage Search Engines by URL Security Vulnerabilities

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

Discourage Search Engines by URL Release Timeline

v0.2.1Current
v0.2
v0.1
Code Analysis
Analyzed Mar 16, 2026

Discourage Search Engines by URL Code Analysis

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

Output Escaping

20% escaped5 total outputs
Attack Surface

Discourage Search Engines by URL Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionwp_headdiscourage-search-engines-by-url.php:38
actionadmin_bar_menudiscourage-search-engines-by-url.php:41
actionadmin_initdiscourage-search-engines-by-url.php:44
Maintenance & Trust

Discourage Search Engines by URL Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.33
Last updatedJan 6, 2017
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs80
Developer Profile

Discourage Search Engines by URL Developer Profile

Storm Rockwell

2 plugins · 280 total installs

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

How We Detect Discourage Search Engines by URL

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
dashicons-visibilitydashicons-beforedashicons-dashboard
Data Attributes
id="dseburl_url"name="dseburl_url"id="dseburl_hide_icon"name="dseburl_hide_icon"id="dseburl"id="dseburl-group"+3 more
FAQ

Frequently Asked Questions about Discourage Search Engines by URL