DomainLabs Whois Security & Risk Analysis

wordpress.org/plugins/domainlabs-whois

DomainLabs Domain Whois Plugin for Wordpress

30 active installs v1.0.3 PHP + WP 3.0+ Updated Jan 8, 2015
domainsearchwhoiswhois-searchwp-whois
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is DomainLabs Whois Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 11yr ago
Risk Assessment

The domainlabs-whois v1.0.3 plugin presents a generally strong security posture, particularly concerning its attack surface. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the potential entry points for attackers. Furthermore, the code analysis indicates a commitment to secure coding practices, with no dangerous functions or file operations detected, and all SQL queries utilizing prepared statements. The plugin also avoids external HTTP requests, which can sometimes introduce vulnerabilities. However, a notable concern arises from the output escaping, where only 36% of outputs are properly escaped. This leaves a significant portion of the plugin's output potentially vulnerable to cross-site scripting (XSS) attacks if user-supplied data is not handled with extreme care before being rendered on a page. The lack of any recorded vulnerability history is a positive indicator, suggesting a history of secure development or diligent patching by the developers, but it does not negate the identified output escaping weakness. In conclusion, while the plugin demonstrates good practices in limiting attack surface and secure data handling for SQL, the insufficient output escaping is a clear area of concern that requires immediate attention to mitigate potential XSS risks.

Key Concerns

  • Insufficient output escaping
Vulnerabilities
None known

DomainLabs Whois Security Vulnerabilities

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

DomainLabs Whois Release Timeline

v1.0.3Current
v1.0.2.1
v1.0.2
v1.0.1
v1.0
Code Analysis
Analyzed Mar 16, 2026

DomainLabs Whois Code Analysis

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

Output Escaping

36% escaped11 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

2 flows
print_domainwhoisAdminPage (domainlabs-whois.php:264)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

DomainLabs Whois Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionwp_headdomainlabs-whois.php:329
actionadmin_menudomainlabs-whois.php:330
actionplugins_loadeddomainlabs-whois.php:331
filterthe_contentdomainlabs-whois.php:332
Maintenance & Trust

DomainLabs Whois Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedJan 8, 2015
PHP min version
Downloads9K

Community Trust

Rating40/100
Number of ratings2
Active installs30
Developer Profile

DomainLabs Whois Developer Profile

Bahri CANLI

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 DomainLabs Whois

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/domainlabs-whois/domainlabs-whois.css

HTML / DOM Fingerprints

CSS Classes
whois-textwhois-submitwhois-results
Data Attributes
id="wpwhoisfor"id="wpwhoisdomain"
Shortcode Output
%%whoisresults%%
FAQ

Frequently Asked Questions about DomainLabs Whois