Merge Menus Security & Risk Analysis

wordpress.org/plugins/merge-menus

Quickly add the elements of 1 menu on to another

400 active installs v1.1.3 PHP 7.4+ WP 5.8+ Updated Nov 30, 2023
combinemenumerge
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Merge Menus Safe to Use in 2026?

Generally Safe

Score 85/100

Merge Menus has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 2yr ago
Risk Assessment

The merge-menus plugin v1.1.3 exhibits a strong security posture based on the provided static analysis. The absence of dangerous functions, file operations, external HTTP requests, and raw SQL queries is commendable. The high percentage of properly escaped output further reduces the risk of cross-site scripting vulnerabilities. The presence of capability checks on the single AJAX handler, coupled with zero AJAX handlers lacking authentication, indicates a good understanding of secure WordPress development practices for entry points.

While the analysis reveals a clean slate regarding vulnerability history and taint flows, it's important to note the absence of nonce checks on the AJAX handler. Although the handler has capability checks, the lack of nonce verification is a potential weakness that could be exploited in certain scenarios, especially if the plugin handles sensitive data or actions. This is the primary area of concern in an otherwise robustly developed plugin.

In conclusion, merge-menus v1.1.3 is a secure plugin with excellent coding practices. The lack of historical vulnerabilities and critical code signals is highly positive. The only notable weakness identified is the missing nonce check on its sole AJAX handler, which, while not a critical flaw in isolation due to the presence of capability checks, represents a deviation from best practices for protecting AJAX endpoints.

Key Concerns

  • Missing nonce check on AJAX handler
Vulnerabilities
None known

Merge Menus Security Vulnerabilities

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

Merge Menus Code Analysis

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

Output Escaping

93% escaped15 total outputs
Attack Surface

Merge Menus Attack Surface

Entry Points1
Unprotected0

AJAX Handlers 1

authwp_ajax_merge_menu_get_itemsmerge-menus.php:81
WordPress Hooks 4
actionadmin_initmerge-menus.php:78
filterplugin_row_metamerge-menus.php:79
actionadmin_head-nav-menus.phpmerge-menus.php:85
actionplugins_loadedmerge-menus.php:276
Maintenance & Trust

Merge Menus Maintenance & Trust

Maintenance Signals

WordPress version tested6.4.8
Last updatedNov 30, 2023
PHP min version7.4
Downloads5K

Community Trust

Rating100/100
Number of ratings4
Active installs400
Developer Profile

Merge Menus Developer Profile

wphelpdeskuk

4 plugins · 540 total installs

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

How We Detect Merge Menus

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
merge-menussubmit-merge-menus
Data Attributes
id="merge-menus"id="merge-menu"id="submit-merge-menus"
JS Globals
window.wpNavMenu
REST Endpoints
/wp-json/merge-menu-get-items
FAQ

Frequently Asked Questions about Merge Menus