MultiDomain Security & Risk Analysis

wordpress.org/plugins/multidomain

Allows multiple domains to be pointed at a single WordPress install with customization for each.

300 active installs v1.0 PHP + WP 3.0+ Updated Oct 28, 2011
domaindomainsmirroring
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is MultiDomain Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 14yr ago
Risk Assessment

The "multidomain" plugin v1.0 demonstrates a strong adherence to secure coding practices based on the provided static analysis. The absence of dangerous functions, the exclusive use of prepared statements for all SQL queries, and the complete output escaping for all outputs indicate a diligent approach to preventing common vulnerabilities like SQL injection and cross-site scripting. Furthermore, the lack of file operations and external HTTP requests limits potential attack vectors. The zero known CVEs and a clean vulnerability history further contribute to a positive security posture, suggesting the plugin has not been a target or has been developed with security as a priority.

However, there are a few areas that warrant attention despite the overall good standing. The presence of three shortcodes as entry points, while not directly flagged as unprotected, represents a potential area where vulnerabilities could emerge if not carefully handled internally. The complete absence of nonce and capability checks across all entry points is a significant concern. While the static analysis shows no explicit unprotected handlers or routes, shortcodes can still be susceptible to CSRF attacks if they perform actions that modify data or user states without proper authorization checks. The lack of taint analysis data also means that potential vulnerabilities stemming from the handling of user-supplied data, even if seemingly sanitized, cannot be definitively ruled out.

In conclusion, "multidomain" v1.0 is built on a foundation of secure coding principles, excelling in areas like SQL query preparation and output escaping. The plugin's history is clean, which is a positive indicator. Nevertheless, the absence of explicit authorization and nonce checks on its shortcodes, coupled with the limited scope of the provided taint analysis, represents a weakness that could be exploited. Future development should focus on integrating robust authorization mechanisms into all shortcode functionalities to mitigate potential risks.

Key Concerns

  • Missing nonce checks on entry points
  • Missing capability checks on entry points
Vulnerabilities
None known

MultiDomain Security Vulnerabilities

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

MultiDomain Code Analysis

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

MultiDomain Attack Surface

Entry Points3
Unprotected0

Shortcodes 3

[MultiDomain_if] MultiDomain.php:40
[MultiDomain_else] MultiDomain.php:41
[MultiDomain_default] MultiDomain.php:42
WordPress Hooks 2
filtertemplateMultiDomain.php:32
filteroption_stylesheetMultiDomain.php:33
Maintenance & Trust

MultiDomain Maintenance & Trust

Maintenance Signals

WordPress version tested3.2.3
Last updatedOct 28, 2011
PHP min version
Downloads15K

Community Trust

Rating86/100
Number of ratings6
Active installs300
Developer Profile

MultiDomain Developer Profile

nathancarnes

1 plugin · 300 total installs

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

How We Detect MultiDomain

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
[MultiDomain_if][/MultiDomain_if][MultiDomain_else][/MultiDomain_else]
FAQ

Frequently Asked Questions about MultiDomain