eewee restaurant menu Security & Risk Analysis

wordpress.org/plugins/eewee-restaurant-menu

Management of restaurant menus. Composition dish of the day. Create your own dishes with ingredients, prices, ...

10 active installs v1.6.6 PHP + WP 3.1+ Updated Jan 16, 2015
carteeatfoodmenurestaurant
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is eewee restaurant menu Safe to Use in 2026?

Generally Safe

Score 85/100

eewee restaurant menu has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11yr ago
Risk Assessment

The 'eewee-restaurant-menu' v1.6.6 plugin exhibits a mixed security posture. On the positive side, the plugin has a small attack surface with only two entry points (shortcodes) and no AJAX handlers or REST API routes exposed without authentication. It also demonstrates good practices with the vast majority of its SQL queries utilizing prepared statements, and there are no external HTTP requests or dangerous functions identified. Furthermore, the plugin has no known historical vulnerabilities, suggesting a history of stable and potentially secure development.

However, significant concerns arise from the output escaping analysis. With 0% of outputs properly escaped, this indicates a high risk of Cross-Site Scripting (XSS) vulnerabilities. Any user-provided data that is displayed by the plugin without proper sanitization or escaping could be exploited by attackers to inject malicious scripts. Additionally, while the taint analysis shows no critical or high-severity flows, the fact that all 24 analyzed flows have unsanitized paths is concerning, even if they don't immediately translate to critical issues based on this analysis. The complete absence of nonce and capability checks, while not directly exploited in this version, leaves the shortcode entry points vulnerable to authorization bypass and CSRF attacks if they interact with sensitive data or functionality. The file operations, though limited, also warrant careful inspection for potential path traversal or unauthorized access vulnerabilities if not handled with extreme care.

In conclusion, while the plugin is free of known historical vulnerabilities and employs good practices in SQL query handling and limiting its attack surface, the widespread lack of output escaping and the presence of unsanitized taint flows create a significant risk for XSS and potential other injection attacks. The missing nonce and capability checks also represent an oversight in securing the plugin's entry points. Addressing the output escaping and adding proper authorization checks are paramount for improving its security.

Key Concerns

  • 0% properly escaped output
  • All taint flows have unsanitized paths
  • 0 nonce checks
  • 0 capability checks
Vulnerabilities
None known

eewee restaurant menu Security Vulnerabilities

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

eewee restaurant menu Code Analysis

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

SQL Query Safety

98% prepared43 total queries

Output Escaping

0% escaped204 total outputs
Data Flows
24 unsanitized

Data Flow Analysis

24 flows24 with unsanitized paths
<devise> (view\devise.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

eewee restaurant menu Attack Surface

Entry Points2
Unprotected0

Shortcodes 2

[menu] controllers\ShortcodeController.php:8
[laCarte] controllers\ShortcodeController.php:9
WordPress Hooks 3
actionadmin_initcontrollers\AdminController.php:50
actioninitindex.php:40
actionadmin_menuindex.php:119
Maintenance & Trust

eewee restaurant menu Maintenance & Trust

Maintenance Signals

WordPress version tested4.0.38
Last updatedJan 16, 2015
PHP min version
Downloads6K

Community Trust

Rating66/100
Number of ratings3
Active installs10
Developer Profile

eewee restaurant menu Developer Profile

eewee

5 plugins · 50 total installs

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

How We Detect eewee restaurant menu

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/eewee-restaurant-menu/css/style.css

HTML / DOM Fingerprints

Shortcode Output
menulaCarte
FAQ

Frequently Asked Questions about eewee restaurant menu