
PageMenu Security & Risk Analysis
wordpress.org/plugins/page-menuAllow user to select menu and menu items for specific page
Is PageMenu Safe to Use in 2026?
Generally Safe
Score 85/100PageMenu has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The "page-menu" plugin v5.1.4 exhibits a mixed security posture. On the positive side, it demonstrates good practices by exclusively using prepared statements for all SQL queries and avoiding file operations or external HTTP requests. This suggests a level of care in handling data interaction and external dependencies. However, a significant concern arises from the presence of two AJAX handlers that lack proper authorization checks. This creates an exploitable attack surface, as unauthenticated users could potentially trigger these actions.
While the static analysis shows no critical or high-severity taint flows and the plugin has no recorded vulnerability history, the unprotected AJAX endpoints represent a tangible and immediate risk. The absence of known CVEs is encouraging, but it does not negate the inherent insecurity of unprotected entry points. The plugin's strengths in data sanitization and avoidance of risky functions are overshadowed by the vulnerability in its access control for AJAX actions. Therefore, while the plugin appears to follow some secure coding principles, the unprotected AJAX handlers require urgent attention to mitigate potential exploitation.
Key Concerns
- Unprotected AJAX handlers
- Limited output escaping (75%)
PageMenu Security Vulnerabilities
PageMenu Code Analysis
Output Escaping
PageMenu Attack Surface
AJAX Handlers 2
WordPress Hooks 7
Maintenance & Trust
PageMenu Maintenance & Trust
Maintenance Signals
Community Trust
PageMenu Alternatives
PageMenu Developer Profile
2 plugins · 1K total installs
How We Detect PageMenu
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
HTML / DOM Fingerprints
pagemenu-hide