yg-Subdomains Security & Risk Analysis

wordpress.org/plugins/yg-subdomain

YG-Subdomains allows users to setup there specified page as subdomains. It's a lite and fast code.

20 active installs v0.1 PHP + WP 2.8+ Updated Aug 30, 2013
categoriesfake-subdomainsubdomains
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is yg-Subdomains Safe to Use in 2026?

Generally Safe

Score 85/100

yg-Subdomains has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 12yr ago
Risk Assessment

The 'yg-subdomain' plugin v0.1 exhibits a generally positive security posture based on the provided static analysis. The complete absence of known vulnerabilities, including critical and high severity ones, is a significant strength. Furthermore, the code demonstrates good practices by exclusively using prepared statements for SQL queries, implementing nonce checks, and utilizing capability checks. The analysis also indicates no critical or high severity taint flows, suggesting that user-supplied data is handled with reasonable care regarding paths. The lack of file operations and external HTTP requests further minimizes potential attack vectors.

However, a key area for improvement lies in the output escaping. With only two-thirds of outputs properly escaped, there's a moderate risk of cross-site scripting (XSS) vulnerabilities, especially if the unescaped outputs handle user-controlled data. While the attack surface appears minimal with no identified entry points, this could be due to the limited scope of the analysis or a very simple plugin. The absence of any recorded vulnerabilities historically is encouraging, but it's crucial to maintain vigilance and continue to implement robust security practices as the plugin evolves.

In conclusion, 'yg-subdomain' v0.1 is in a strong security position due to its clean vulnerability history and diligent use of secure coding practices like prepared statements and nonces. The primary concern identified is the incomplete output escaping, which warrants attention to prevent potential XSS issues. The lack of historical vulnerabilities is a positive indicator, but the plugin should not become complacent.

Key Concerns

  • Output escaping is not fully implemented
Vulnerabilities
None known

yg-Subdomains Security Vulnerabilities

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

yg-Subdomains Release Timeline

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

yg-Subdomains Code Analysis

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

SQL Query Safety

100% prepared4 total queries

Output Escaping

67% escaped3 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

2 flows
fake_subdomain_save_postdata (yg-subdomain.php:133)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

yg-Subdomains Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actioninityg-subdomain.php:78
actionadd_meta_boxesyg-subdomain.php:79
actionsave_postyg-subdomain.php:80
filterpost_rewrite_rulesyg-subdomain.php:83
filterpost_linkyg-subdomain.php:84
filterpage_rewrite_rulesyg-subdomain.php:85
filterpage_linkyg-subdomain.php:86
filterroot_rewrite_rulesyg-subdomain.php:191
Maintenance & Trust

yg-Subdomains Maintenance & Trust

Maintenance Signals

WordPress version tested3.6.1
Last updatedAug 30, 2013
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings1
Active installs20
Developer Profile

yg-Subdomains Developer Profile

DragonOfDev

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 yg-Subdomains

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

Asset Fingerprints

HTML / DOM Fingerprints

HTML Comments
<!-- Use nonce for verification --><!-- The actual fields for data entry --><!-- Use get_post_meta to retrieve an existing value from the database and use the value for the form --><!-- First we need to check if the current user is authorised to do this action. -->+5 more
Data Attributes
name="fake_subdomain_noncename"id="fake_subdomain_new_check"name="fake_subdomain_new_check"value="fake_subdomain"id="fake_subdomain_new_field"name="fake_subdomain_new_field"
FAQ

Frequently Asked Questions about yg-Subdomains