Menus for Block Theme Security & Risk Analysis

wordpress.org/plugins/menus-for-block-theme

Menus for Block Theme add a setting page in the WordPress dashboard (Settings > MFBT Settings) which allows managing the following options :

50 active installs v1.0.0 PHP 5.4+ WP 6.0+ Updated May 16, 2023
custom-menucustomizerfile-editorfull-site-editingmenu
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Menus for Block Theme Safe to Use in 2026?

Generally Safe

Score 85/100

Menus for Block Theme 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

Based on the provided static analysis and vulnerability history, the "menus-for-block-theme" plugin version 1.0.0 demonstrates a strong initial security posture. The plugin exhibits zero identified entry points such as AJAX handlers, REST API routes, or shortcodes that are accessible without proper authentication or permission checks. Furthermore, the code analysis reveals a complete absence of dangerous functions, file operations, and external HTTP requests, indicating a limited and well-contained codebase. All detected SQL queries are properly prepared, and output escaping is consistently applied, which are excellent practices for preventing common vulnerabilities like SQL injection and Cross-Site Scripting (XSS). The lack of any recorded CVEs, past or present, further contributes to this positive assessment.

However, a significant concern arises from the complete lack of nonce checks and capability checks, alongside zero identified entry points. While the current version may not have exposed them, the absence of these fundamental security mechanisms means that if any new entry points are introduced in future updates, they would be inherently unprotected. This signifies a potential for future vulnerabilities to be introduced if these checks are not implemented as the plugin evolves. The plugin's strengths lie in its clean code and absence of known vulnerabilities, but its weakness is the foundational lack of input validation and authorization checks, which could become critical if its attack surface expands.

Key Concerns

  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Menus for Block Theme Security Vulnerabilities

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

Menus for Block Theme Code Analysis

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

Output Escaping

100% escaped2 total outputs
Attack Surface

Menus for Block Theme Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actionadmin_headincludes\main.php:25
actionadmin_menuincludes\main.php:33
actionadmin_menuincludes\main.php:37
actionadmin_menuincludes\main.php:41
actionadmin_menuincludes\main.php:45
actionadmin_menumenus-for-block-theme.php:39
actionadmin_initmenus-for-block-theme.php:40
actioninitmenus-for-block-theme.php:41
Maintenance & Trust

Menus for Block Theme Maintenance & Trust

Maintenance Signals

WordPress version tested6.2.9
Last updatedMay 16, 2023
PHP min version5.4
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs50
Developer Profile

Menus for Block Theme Developer Profile

La Webeuse

1 plugin · 50 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 for Block Theme

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/menus-for-block-theme/css/admin.css/wp-content/plugins/menus-for-block-theme/js/admin.js
Script Paths
/wp-content/plugins/menus-for-block-theme/js/admin.js
Version Parameters
menus-for-block-theme/css/admin.css?ver=menus-for-block-theme/js/admin.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Menus for Block Theme