Menus History Security & Risk Analysis

wordpress.org/plugins/menus-history

Provides history of changes to Wordpress menus

70 active installs v1.0.2 PHP + WP 3.5+ Updated May 24, 2015
menu-historymenu-revisionmenu-revisionsmenusmenus-history
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Menus History Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 10yr ago
Risk Assessment

The "menus-history" plugin v1.0.2 exhibits several critical security weaknesses despite its clean vulnerability history and absence of dangerous functions. The most significant concern is the presence of two AJAX handlers that lack any authentication or capability checks. This creates a substantial attack surface, allowing any authenticated user, regardless of their role or privileges, to potentially trigger these handlers, leading to unintended actions or data manipulation. Furthermore, the analysis indicates that 100% of the plugin's outputs are not properly escaped. This leaves the plugin vulnerable to Cross-Site Scripting (XSS) attacks, where malicious scripts could be injected and executed in the user's browser, potentially compromising their session or data.

While the plugin's clean vulnerability history is a positive indicator and the use of prepared statements for SQL queries is commendable, these strengths are heavily overshadowed by the identified security flaws. The absence of taint analysis results is noted, but this does not negate the clear risks presented by the unprotected AJAX endpoints and unescaped output. The plugin's overall security posture is therefore concerning due to the high potential for exploitation through readily accessible entry points and output vulnerabilities.

Key Concerns

  • AJAX handlers without auth checks
  • Output escaping: 0% properly escaped
  • Total entry points: 2, Unprotected: 2
Vulnerabilities
None known

Menus History Security Vulnerabilities

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

Menus History Code Analysis

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

Output Escaping

0% escaped7 total outputs
Attack Surface
2 unprotected

Menus History Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_get_revisionsclasses\class-menus-history-controller.php:16
authwp_ajax_get_revisionclasses\class-menus-history-controller.php:19
WordPress Hooks 5
actionwp_update_nav_menuclasses\class-menus-history-controller.php:10
actionadmin_menuclasses\class-menus-history-controller.php:13
actionadmin_enqueue_scriptsclasses\class-menus-history-controller.php:22
actioninitmenus-history.php:34
actionplugins_loadedmenus-history.php:46
Maintenance & Trust

Menus History Maintenance & Trust

Maintenance Signals

WordPress version tested4.2.39
Last updatedMay 24, 2015
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs70
Developer Profile

Menus History Developer Profile

binarystash01

1 plugin · 70 total installs

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

How We Detect Menus History

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/menus-history/js/menus-history.js/wp-content/plugins/menus-history/css/menus-history.css
Script Paths
/wp-content/plugins/menus-history/js/menus-history.js
Version Parameters
menus-history.js?ver=menus-history.css?ver=

HTML / DOM Fingerprints

CSS Classes
latest
Data Attributes
name="menus-history-revision"
FAQ

Frequently Asked Questions about Menus History