WP Subdomains (Revisited) Security & Risk Analysis

wordpress.org/plugins/wp-subdomains-revisited

Setup your main categories, pages, and authors as subdomains with custom themes. Surely will come for more options...

30 active installs v0.9.3 PHP + WP 3.0+ Updated Feb 26, 2013
categoriespostpostssubdomainsubdomains
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Subdomains (Revisited) Safe to Use in 2026?

Generally Safe

Score 85/100

WP Subdomains (Revisited) has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 13yr ago
Risk Assessment

The plugin "wp-subdomains-revisited" v0.9.3 presents a generally positive security posture, particularly due to its minimal attack surface and lack of known historical vulnerabilities. The static analysis reveals no identified AJAX handlers, REST API routes, shortcodes, or cron events, which significantly reduces the plugin's exposure to common attack vectors. Furthermore, the absence of dangerous function usage and file operations is a strong indicator of good coding practices.

However, there are areas for concern within the code itself. A significant portion of SQL queries (83%) are not using prepared statements, which could lead to SQL injection vulnerabilities if user input is not properly sanitized before being incorporated into these queries. The complete lack of proper output escaping (0%) is a critical weakness, exposing the plugin to potential Cross-Site Scripting (XSS) vulnerabilities. While only two taint flows were analyzed, the absence of critical or high severity issues in this specific analysis is a positive sign, but it does not negate the risks posed by unescaped output and raw SQL queries.

The plugin's vulnerability history being entirely clean, with no recorded CVEs or past vulnerabilities, suggests a history of secure development or at least a lack of publicly disclosed issues. This, combined with the presence of nonce and capability checks, builds some confidence. Nevertheless, the identified weaknesses in SQL query preparation and especially output escaping warrant attention to prevent potential security incidents.

Key Concerns

  • Raw SQL queries without prepared statements
  • No output escaping
Vulnerabilities
None known

WP Subdomains (Revisited) Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

WP Subdomains (Revisited) Code Analysis

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

SQL Query Safety

17% prepared24 total queries

Output Escaping

0% escaped29 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
wps_settings_settings (plugin\admin.php:54)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP Subdomains (Revisited) Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 42
filterplugin_action_linksplugin\admin.php:457
filtercontextual_helpplugin\admin.php:458
actionadmin_menusubdomains.php:119
actionadmin_initsubdomains.php:131
actioninitsubdomains.php:138
actionwpsubdomains.php:140
actioncategory_edit_form_fieldssubdomains.php:143
actionedited_categorysubdomains.php:144
actioncategory_add_form_fieldssubdomains.php:145
actionedited_categorysubdomains.php:146
actiondo_meta_boxessubdomains.php:148
actionsave_postsubdomains.php:149
actionparse_querysubdomains.php:151
filterrewrite_rules_arraysubdomains.php:157
filterroot_rewrite_rulessubdomains.php:158
filterpost_rewrite_rulessubdomains.php:159
filterpage_rewrite_rulessubdomains.php:160
filterdate_rewrite_rulessubdomains.php:161
filtertag_rewrite_rulessubdomains.php:162
filtercategory_rewrite_rulessubdomains.php:163
filterauthor_rewrite_rulessubdomains.php:164
filterget_previous_post_joinsubdomains.php:170
filterget_next_post_joinsubdomains.php:171
filterget_previous_post_wheresubdomains.php:172
filterget_next_post_wheresubdomains.php:173
filtergetarchives_joinsubdomains.php:176
filtergetarchives_wheresubdomains.php:177
filterpre_option_templatesubdomains.php:179
filterpre_option_stylesheetsubdomains.php:180
filterget_pagessubdomains.php:185
filterbloginfo_urlsubdomains.php:188
filterbloginfosubdomains.php:189
filtercategory_linksubdomains.php:190
filterpost_linksubdomains.php:191
filterpage_linksubdomains.php:192
filterauthor_linksubdomains.php:193
filtertag_linksubdomains.php:194
filtermonth_linksubdomains.php:195
filterget_pagenum_linksubdomains.php:196
filterlist_catssubdomains.php:197
actionwidgets_initwidgets\categories.php:132
actionwidgets_initwidgets\sitelist.php:144
Maintenance & Trust

WP Subdomains (Revisited) Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedFeb 26, 2013
PHP min version
Downloads14K

Community Trust

Rating94/100
Number of ratings3
Active installs30
Developer Profile

WP Subdomains (Revisited) Developer Profile

lontongcorp

2 plugins · 40 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 Subdomains (Revisited)

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-subdomains-revisited/plugin/admin.css/wp-content/plugins/wp-subdomains-revisited/plugin/admin.js
Script Paths
/wp-content/plugins/wp-subdomains-revisited/plugin/admin.js
Version Parameters
wp-subdomains-revisited/plugin/admin.css?ver=wp-subdomains-revisited/plugin/admin.js?ver=

HTML / DOM Fingerprints

CSS Classes
wps-admin-settings
Data Attributes
data-wps-id
JS Globals
wps_admin
FAQ

Frequently Asked Questions about WP Subdomains (Revisited)