CVE-2022-3776
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Restaurant Menu – Food Ordering System – Table Reservation plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.3.1. This is due to missing or incorrect nonce validation on several functions called via AJAX actions such as forms_action, set_option, & chosen_options to name a few . This makes it possible for unauthenticated attackers to perform a variety of administrative actions like modifying forms, via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Restaurant Menu – Food Ordering System – Table Reservation WordPress plugin versions up to 2.3.1 lacks proper nonce validation on multiple AJAX action handlers (forms_action, set_option, chosen_options). This allows unauthenticated attackers to forge administrative requests by tricking logged-in site administrators into clicking malicious links, enabling unauthorized modification of plugin settings and forms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if the Restaurant Menu plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Restaurant Menu - Food Ordering System - Table Reservation', or inspect the plugin directory wp-content/plugins/ for a folder containing 'restaurant-menu' or similar namingAffected if The plugin is installed and active
-
Identify the installed plugin versionIn WordPress admin Plugins list, click on the plugin name to view its details and version number, or read the main plugin PHP file header for 'Version:' tagAffected if Version is 2.3.1 or lower (vulnerable range is < 2.3.2)
-
Test AJAX endpoint accessibilityCheck if the WordPress site responds to admin-ajax.php requests with action parameters: forms_action, set_option, or chosen_options. Send a request like: https://yoursite.com/wp-admin/admin-ajax.php?action=forms_actionAffected if The AJAX endpoints respond and accept parameters without requiring valid nonce validation (an attacker could trigger these without authentication if they can trick a logged-in admin)
-
Inspect AJAX handler code for nonce validationLocate the plugin PHP files handling AJAX actions (forms_action, set_option, chosen_options) and examine if they call wp_verify_nonce or check_admin_referer before processing requestsAffected if The AJAX handlers lack proper nonce verification logic (no wp_verify_nonce or check_admin_referer calls present)
-
Verify plugin configuration exposureReview if plugin settings and form data can be modified via the vulnerable AJAX actions by an unauthenticated request when triggered through a logged-in admin sessionAffected if Settings or form content can be altered without proper authentication tokens
You are affected if the Restaurant Menu plugin versions 2.3.1 or below are installed and the AJAX handlers for forms_action, set_option, or chosen_options lack proper nonce validation checks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.3.2
Update the plugin to a version beyond 2.3.1 which includes proper nonce validation on AJAX handlers. Until then, avoid clicking untrusted links while logged into the WordPress admin panel.
Restaurant Menu – Food Ordering System – Table Reservation plugin version 2.3.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Restaurant Menu – Food Ordering System – Table Reservation' plugin
- Check if the current version is below 2.3.2
- If vulnerable, click 'Update Now' to upgrade to version 2.3.2 or latest available version
- After updating, verify the plugin version is 2.3.2 or higher in the plugins list
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3776 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-3776 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data