dbcve.org
Great Restaurant Menu WpWordPress extension · Pricelisto

CVE-2024-38793

HIGH · 8.8 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 1.4.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in PriceListo Best Restaurant Menu by PriceListo allows SQL Injection.This issue affects Best Restaurant Menu by PriceListo: from n/a through 1.4.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 confidence

A SQL injection vulnerability exists in the Best Restaurant Menu by PriceListo plugin (versions up to 1.4.1) due to improper neutralization of special elements in SQL commands. An attacker could inject malicious SQL queries through unsanitized input parameters to manipulate the application's database, potentially extracting, modifying, or deleting data.

MitigationFix requires identifying and sanitizing all user-supplied input that is used in database queries by implementing parameterized queries or prepared statements instead of dynamic SQL construction.

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
Great Restaurant Menu WpWordPress extension
Affected:< 1.4.2

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > locate 'Best Restaurant Menu by PriceListo' (or 'Pricelisto Great Restaurant Menu Wp') and note the version number displayed
    Affected if The version shown is lower than 1.4.2 (e.g., 1.4.1, 1.4.0, etc.)
  2. Verify the plugin is active
    Confirm the plugin status shows as 'Active' in the Plugins page
    Affected if The plugin is active and the version is below 1.4.2
  3. Inspect plugin files for SQL query handling
    Access the plugin directory via FTP or file manager (wp-content/plugins/pricelisto-great-restaurant-menu or similar) and examine PHP files that handle database queries, looking for direct SQL construction with user-supplied parameters
    Affected if Files contain SQL queries that incorporate $_GET, $_POST, or $_REQUEST variables without using prepared statements or sanitization functions
  4. Check for unsanitized input in search or filter features
    Review plugin PHP files for endpoints that process search queries, category filters, or menu lookups, noting if $_GET parameters like 's', 'search', 'category', or 'id' are inserted directly into SQL statements
    Affected if User-supplied parameters from URL or form inputs are concatenated directly into SQL queries without escaping or parameter binding

You are affected if the plugin is installed and active with a version lower than 1.4.2, and your site processes user input through the plugin's database query functions without parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.4.2 or later
Fixed in 1.4.2
Interim mitigation

Fix requires identifying and sanitizing all user-supplied input that is used in database queries by implementing parameterized queries or prepared statements instead of dynamic SQL construction.

Recommended fix High confidence

1.4.2

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate 'Great Restaurant Menu WP' or 'Best Restaurant Menu by PriceListo' plugin
  4. Click 'Update now' to upgrade to version 1.4.2
  5. Verify the plugin version shows 1.4.2 after updating
  6. Test that the plugin functionality works correctly on your site

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Great Restaurant Menu Wp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38793 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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