siteselector Security & Risk Analysis

wordpress.org/plugins/siteselector

siteselector plugin helps you choose a domain name, check it's availability and see your competition

30 active installs v1.01 PHP + WP 3.2+ Updated Aug 9, 2017
administrationdomain-nameweb-hosting
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is siteselector Safe to Use in 2026?

Generally Safe

Score 85/100

siteselector 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 "siteselector" plugin v1.01 exhibits several significant security concerns, primarily stemming from a large unprotected attack surface and poor output sanitization. While the plugin does not appear to have a history of known vulnerabilities (CVEs), this does not inherently mean it is secure. The static analysis reveals 6 out of 7 entry points are unprotected, with 6 AJAX handlers lacking authentication checks. This creates a substantial risk for unauthorized actions to be performed on a WordPress site. Furthermore, a very low percentage (3%) of output is properly escaped, indicating a high likelihood of Cross-Site Scripting (XSS) vulnerabilities across the plugin's output.

Key Concerns

  • Unprotected AJAX handlers
  • Low output escaping percentage
  • No nonce checks on entry points
  • No capability checks on entry points
  • Unsanitized paths in taint flows
  • SQL queries not always prepared
Vulnerabilities
None known

siteselector Security Vulnerabilities

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

siteselector Release Timeline

No version history available.
Code Analysis
Analyzed Mar 16, 2026

siteselector Code Analysis

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

SQL Query Safety

42% prepared12 total queries

Output Escaping

3% escaped32 total outputs
Data Flows · Security
3 unsanitized

Data Flow Analysis

4 flows3 with unsanitized paths
siteselector_find_names (siteselector_functions.php:151)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
6 unprotected

siteselector Attack Surface

Entry Points7
Unprotected6

AJAX Handlers 6

noprivwp_ajax_siteselector_ajax_initializesiteselector_functions.php:139
authwp_ajax_siteselector_ajax_initializesiteselector_functions.php:140
noprivwp_ajax_siteselector_find_namessiteselector_functions.php:149
authwp_ajax_siteselector_find_namessiteselector_functions.php:150
noprivwp_ajax_siteselector_check_urlsiteselector_functions.php:176
authwp_ajax_siteselector_check_urlsiteselector_functions.php:177

Shortcodes 1

[siteselector] siteselector_functions.php:207
WordPress Hooks 5
actionadmin_initsiteselector_functions.php:60
actioninitsiteselector_functions.php:61
actionadmin_menusiteselector_functions.php:79
actionadmin_headsiteselector_functions.php:554
actionwp_footersiteselector_functions.php:555
Maintenance & Trust

siteselector Maintenance & Trust

Maintenance Signals

WordPress version tested4.3.34
Last updatedAug 9, 2017
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

siteselector Developer Profile

scideas

1 plugin · 30 total installs

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

How We Detect siteselector

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/siteselector/siteselector_plugin.js
Script Paths
/wp-content/plugins/siteselector/siteselector_plugin.js

HTML / DOM Fingerprints

JS Globals
siteselector_URL
FAQ

Frequently Asked Questions about siteselector