The Quick Restaurant Menu plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on its AJAX actions in versions up to, and including, 2.0.2. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to...
Product
wordpress quick-restaurant-menu vulnerabilities
5 published CVES affecting wordpress quick-restaurant-menu, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 0
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress quick-restaurant-menu CVEs
Newest publication first
-
MediumCVSS 5.4 EPSS 0.61%
-
MediumCVSS 4.3 EPSS 0.37%
The Quick Restaurant Menu plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0.2. This is due to missing or incorrect nonce validation on its AJAX actions. This makes it possible for unauthenticated attackers to update menu items,...
-
CVE-2023-0553 Quick Restaurant Menu <= 2.0.2 - Authenticated (Administrator+) Cross-Site Scripting
PublishedMediumCVSS 4.8 EPSS 0.56%The Quick Restaurant Menu plugin for WordPress is vulnerable to Stored Cross-Site Scripting via its settings parameters in versions up to, and including, 2.0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with adm...
-
MediumCVSS 4.3 EPSS 0.66%
The Quick Restaurant Menu plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 2.0.2. This is due to the fact that during menu item deletion/modification, the plugin does not verify that the post ID provided to the AJAX action i...
-
MediumCVSS 6.4
The Quick Restaurant Menu plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters in its AJAX actions in versions up to, and including, 2.0.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated atta...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.