Best Restaurant MenuWordPress extension · Pricelisto
CVE-2023-47649
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in PriceListo Best Restaurant Menu by PriceListo.This issue affects Best Restaurant Menu by PriceListo: from n/a through 1.3.1.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Best Restaurant Menu by PriceListo WordPress plugin affecting versions up to 1.3.1. The vulnerability allows attackers to trick authenticated administrators into performing unintended state-changing actions (such as menu modifications) by exploiting the absence of anti-CSRF token validation on sensitive form submissions and AJAX endpoints.
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
Best Restaurant MenuWordPress extension
<= 1.3.1CVSS 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.
-
Identify installed plugin versionNavigate to WordPress Admin > Plugins > Installed Plugins > Pricelisto Best Restaurant Menu, or check the plugin's main PHP file (usually in wp-content/plugins/best-restaurant-menu-pricelisto/) for the Version header in the plugin comment blockAffected if Installed version is 1.3.1 or lower
-
Verify plugin is active with admin accessConfirm the plugin is activated in WordPress and you have administrator-level access to access admin panels and make menu modificationsAffected if Plugin is active and you are logged in as administrator
-
Inspect plugin AJAX handlers for nonce validationExamine the plugin's PHP files (look for add_action("wp_ajax_...") calls) and verify whether the handlers call wp_verify_nonce() or check_admin_referer() before processing requestsAffected if AJAX endpoints lack nonce verification code (wp_verify_nonce or check_admin_referer calls) and process requests without token validation
-
Inspect admin form submissions for CSRF tokensView page source of plugin admin pages (menu management, settings) and check if HTML forms include hidden nonce fields (name containing '_wpnonce' or 'nonce')Affected if Forms that modify menu items or plugin settings do not contain nonce token fields
-
Check for SameSite cookie attributes and header validationReview plugin code for SameSite attribute on setcookie() calls and Origin/Referer header validation in form/AJAX handlersAffected if No SameSite cookie attributes are set and no Origin/Referer header checks are performed before processing state-changing requests
A user is affected if the plugin version is 1.3.1 or lower and the plugin code does not implement nonce validation on AJAX endpoints and admin forms.
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.
From vendor dataImplement anti-CSRF tokens (nonces) on all state-changing forms and AJAX actions within the plugin, verify nonce validation on the server side, and consider adding SameSite cookie attributes and Origin/Referer header checks for additional protection.
Fix this in Best Restaurant Menu
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47649 — 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-2023-47649 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