Redirect multisite user to their own site (UNMAINTAINED) Security & Risk Analysis

wordpress.org/plugins/redirect-multisite-user-to-their-own-site

Redirect a multisite user to their own site.

10 active installs v1.1.2 PHP + WP 4.5+ Updated Nov 11, 2022
multisiteparse_requestredirectuserwpmu
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Redirect multisite user to their own site (UNMAINTAINED) Safe to Use in 2026?

Generally Safe

Score 85/100

Redirect multisite user to their own site (UNMAINTAINED) has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 3yr ago
Risk Assessment

The plugin 'redirect-multisite-user-to-their-own-site' v1.1.2 demonstrates an exceptionally strong security posture based on the provided static analysis. The absence of any identified entry points, including AJAX handlers, REST API routes, shortcodes, and cron events, significantly reduces the potential attack surface. Furthermore, the code analysis reveals no dangerous functions, all SQL queries utilize prepared statements, and all output is properly escaped. The lack of file operations and external HTTP requests further bolsters its security. Taint analysis also shows no identified flows with unsanitized paths, indicating a lack of common vulnerabilities like cross-site scripting (XSS) or path traversal.

The plugin's vulnerability history is also clean, with no recorded CVEs of any severity. This, combined with the code analysis, suggests that the developers have implemented robust security practices. However, it's worth noting the complete absence of nonces and capability checks. While the current lack of entry points mitigates the immediate risk, this could become a concern if the plugin were to evolve and introduce new functionalities that might expose these checks.

In conclusion, the 'redirect-multisite-user-to-their-own-site' v1.1.2 plugin appears to be very secure, with a commendable absence of common vulnerabilities and a minimal attack surface. The developers have clearly prioritized security in its current implementation. The only minor area for potential future consideration would be the implementation of nonces and capability checks if the plugin's feature set expands.

Vulnerabilities
None known

Redirect multisite user to their own site (UNMAINTAINED) Security Vulnerabilities

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

Redirect multisite user to their own site (UNMAINTAINED) Release Timeline

v1.1.2Current
v1.1.1
v1.1.0
v1.0.1
v1.0.0
Code Analysis
Analyzed Apr 16, 2026

Redirect multisite user to their own site (UNMAINTAINED) 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

Redirect multisite user to their own site (UNMAINTAINED) Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionparse_requestPlugin.php:20
Maintenance & Trust

Redirect multisite user to their own site (UNMAINTAINED) Maintenance & Trust

Maintenance Signals

WordPress version tested4.6.30
Last updatedNov 11, 2022
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Redirect multisite user to their own site (UNMAINTAINED) Developer Profile

Mark Howells-Mead

10 plugins · 2K total installs

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

How We Detect Redirect multisite user to their own site (UNMAINTAINED)

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Redirect multisite user to their own site (UNMAINTAINED)