IF Menu Visibility Security & Risk Analysis

wordpress.org/plugins/if-menu-visibility

Add login-based visibility control to WordPress menus. Show or hide menu items depending on whether users are logged in or not.

30 active installs v1.0.5 PHP + WP 5.0+ Updated Dec 12, 2025
conditional-menuif-menulogged-inlogged-outmenu-visibility
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is IF Menu Visibility Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 3mo ago
Risk Assessment

The "if-menu-visibility" plugin, version 1.0.5, demonstrates a strong security posture based on the provided static analysis and vulnerability history. The absence of any AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface, with zero identified unprotected entry points. The code analysis reveals excellent adherence to security best practices, including 100% proper output escaping, 100% of SQL queries using prepared statements, and the presence of both nonce and capability checks.

Furthermore, the plugin has no recorded vulnerabilities (CVEs) and no flagged taint analysis flows, indicating a clean codebase without apparent critical or high-severity flaws. The lack of file operations and external HTTP requests further minimizes potential vectors for compromise. This robust set of positive indicators suggests a well-developed and secure plugin that prioritizes user safety.

While the plugin's current state is highly secure, it's important to maintain vigilance. The absence of past vulnerabilities is a positive sign, but ongoing security audits and prompt updates for any future discoveries would be prudent. For now, the plugin presents a very low risk to WordPress installations.

Vulnerabilities
None known

IF Menu Visibility Security Vulnerabilities

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

IF Menu Visibility Code Analysis

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

Output Escaping

100% escaped7 total outputs
Attack Surface

IF Menu Visibility Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
filtermanage_nav-menus_columnsif-menu-visibility.php:15
filterget_user_option_managenav-menuscolumnshiddenif-menu-visibility.php:21
filterwp_edit_nav_menu_walkerif-menu-visibility.php:28
filterwp_setup_nav_menu_itemif-menu-visibility.php:98
filterwp_nav_menu_objectsif-menu-visibility.php:104
actionwp_nav_menu_item_custom_fieldsif-menu-visibility.php:117
actionwp_update_nav_menu_itemif-menu-visibility.php:135
actionadmin_noticesif-menu-visibility.php:160
filterplugin_action_links_if-menu-visibility/if-menu-visibility.phpif-menu-visibility.php:172
Maintenance & Trust

IF Menu Visibility Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedDec 12, 2025
PHP min version
Downloads476

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

IF Menu Visibility Developer Profile

Valeri Kluger

2 plugins · 530 total installs

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

How We Detect IF Menu Visibility

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/if-menu-visibility/if-menu-visibility.php

HTML / DOM Fingerprints

CSS Classes
field-if-menu-visibility
Data Attributes
name="menu-item-if-visibilityid="edit-menu-item-if-visibility-
FAQ

Frequently Asked Questions about IF Menu Visibility