
Different Home for Logged IN & Logged OUT Security & Risk Analysis
wordpress.org/plugins/different-home-for-logged-in-logged-outSet different Homepage for your Logged IN and Logged OUT users. Increase your engagement, and let your users see what they should be seeing.
Is Different Home for Logged IN & Logged OUT Safe to Use in 2026?
Generally Safe
Score 92/100Different Home for Logged IN & Logged OUT has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The plugin "different-home-for-logged-in-logged-out" v2.0.1 exhibits a generally positive security posture based on the provided static analysis. The complete absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the potential attack surface. Furthermore, the plugin demonstrates good practices by utilizing prepared statements for its single SQL query and employing capability checks.
However, some areas warrant attention. The taint analysis revealed two flows with unsanitized paths, which, while not classified as critical or high severity in this analysis, represent a potential risk if these paths are directly exposed to user input without proper sanitization. Additionally, while 100% of SQL queries use prepared statements, the output escaping is only properly implemented for 69% of outputs, leaving a portion of data potentially vulnerable to XSS attacks if not handled carefully elsewhere. The plugin also bundles Freemius v1.0, which may be an outdated version depending on its current release and any known vulnerabilities within it.
The complete lack of any recorded vulnerabilities in its history is a strong positive indicator, suggesting a commitment to security or a lack of significant past issues. In conclusion, the plugin has a solid foundation with a minimal attack surface and good database practices. The primary areas of concern are the unsanitized paths identified in the taint analysis and the incomplete output escaping, which should be addressed to further strengthen its security.
Key Concerns
- Taint analysis: 2 flows with unsanitized paths
- Output escaping: 31% not properly escaped
- Bundled library: Freemius v1.0 potentially outdated
Different Home for Logged IN & Logged OUT Security Vulnerabilities
Different Home for Logged IN & Logged OUT Code Analysis
Bundled Libraries
SQL Query Safety
Output Escaping
Data Flow Analysis
Different Home for Logged IN & Logged OUT Attack Surface
WordPress Hooks 4
Maintenance & Trust
Different Home for Logged IN & Logged OUT Maintenance & Trust
Maintenance Signals
Community Trust
Different Home for Logged IN & Logged OUT Alternatives
Widget Options – Advanced Conditional Visibility for Gutenberg Blocks & Classic Widgets
widget-options
0ddcemmihs4a843ekhaoofzosrunf4bl Widget Options gives you super powers to control your site’s sidebar widgets and all Gutenberg blocks on pages, posts …
If Menu – Visibility control for Menus
if-menu
Display tailored menu items to each visitor with visibility rules
If Widget – Visibility control for Widgets
if-widget
Control what widgets your site’s visitors see, with custom visibility rules
Speculative Loading
speculation-rules
Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction.
Block Visibility — Conditional Visibility Control for the Block Editor
block-visibility
Easily show or hide any WordPress block. Schedule block visibility. Restrict blocks to specific screen sizes, user roles, post types, and more.
Different Home for Logged IN & Logged OUT Developer Profile
7 plugins · 340 total installs
How We Detect Different Home for Logged IN & Logged OUT
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/different-home-for-logged-in-logged-out/assets/css/admin.css/wp-content/plugins/different-home-for-logged-in-logged-out/assets/js/admin.jsdifferent-home-for-logged-in-logged-out/assets/css/admin.css?ver=different-home-for-logged-in-logged-out/assets/js/admin.js?ver=HTML / DOM Fingerprints
diff_home_settings_pagedata-dh-field