Restrict Multisite Plugins Security & Risk Analysis

wordpress.org/plugins/restrict-multisite-plugins

Allows network admins to restrict which plugins are available on sites, similar to themes.

10 active installs v1.1.3 PHP + WP 3.0+ Updated Jun 30, 2011
multisitepluginsrestrict
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Restrict Multisite Plugins Safe to Use in 2026?

Generally Safe

Score 85/100

Restrict Multisite Plugins 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 "restrict-multisite-plugins" plugin version 1.1.3 exhibits a strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the potential attack surface. Furthermore, the code demonstrates good practices with 100% of SQL queries using prepared statements and the presence of at least one capability check. The taint analysis also shows no identified unsanitized flows, indicating a low risk of remote code execution or arbitrary file reads through tainted input.

However, a significant concern arises from the very low percentage of properly escaped output (11%). This suggests a high likelihood of Cross-Site Scripting (XSS) vulnerabilities. While there are no recorded historical vulnerabilities, the lack of robust output escaping is a critical weakness that could be exploited by attackers to inject malicious scripts into the WordPress admin area or public-facing sites. The plugin's vulnerability history being clean is a positive sign, but it should not overshadow the clear risk identified in the output escaping metrics.

In conclusion, the plugin's limited attack surface and secure handling of SQL and taint are commendable. However, the poor output escaping is a substantial security flaw that requires immediate attention. Without addressing this, the plugin remains susceptible to XSS attacks, despite its other strengths. The plugin's overall security is undermined by this single, albeit significant, weakness.

Key Concerns

  • Low output escaping percentage (11%)
Vulnerabilities
None known

Restrict Multisite Plugins Security Vulnerabilities

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

Restrict Multisite Plugins Code Analysis

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

Output Escaping

11% escaped9 total outputs
Attack Surface

Restrict Multisite Plugins Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
filterall_pluginsrestrict-multisite-plugins.php:147
actionnetwork_admin_menurestrict-multisite-plugins.php:153
actionadmin_menurestrict-multisite-plugins.php:155
Maintenance & Trust

Restrict Multisite Plugins Maintenance & Trust

Maintenance Signals

WordPress version tested3.2.1
Last updatedJun 30, 2011
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Restrict Multisite Plugins Developer Profile

Adam Harley (Kawauso)

8 plugins · 600 total installs

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

How We Detect Restrict Multisite Plugins

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

Asset Fingerprints

HTML / DOM Fingerprints

Data Attributes
plugin[id="enabled_id="disabled_
FAQ

Frequently Asked Questions about Restrict Multisite Plugins