CVE-2026-57644
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 · uneditedContributor SQL Injection in Restaurant Menu by MotoPress <= 2.4.10 versions.
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 confidenceA SQL injection vulnerability in the Restaurant Menu plugin by MotoPress versions 2.4.10 and below allows authenticated users with Contributor-level permissions to inject malicious SQL queries through unsanitized input parameters, potentially enabling data exfiltration or manipulation of the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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.
-
Locate the Restaurant Menu by MotoPress plugin filesNavigate to the wp-content/plugins/ directory in your WordPress installation and look for a folder containing 'restaurant-menu' or 'motopress' in the name. The main plugin file typically contains the version declaration.Affected if The plugin folder exists in the plugins directory.
-
Determine the installed plugin versionOpen the main plugin PHP file (often named index.php, main.php, or similar at the root of the plugin folder) and search for a version constant or comment at the top of the file. Alternatively, in the WordPress admin go to Plugins > Installed Plugins and look for the version listed next to Restaurant Menu by MotoPress.Affected if The displayed version is 2.4.10 or any version lower than 2.4.10.
-
Verify the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and confirm whether Restaurant Menu by MotoPress shows as 'Active'. You can also query the wp_options table for the option_name 'active_plugins' to see if the plugin is enabled.Affected if The plugin is active and the version is 2.4.10 or below.
-
Check for contributor-level or higher user accountsIn the WordPress admin, navigate to Users and review the role assigned to each user. Contributor role and any role above it (author, editor, administrator) can exploit this vulnerability. You can also query the wp_usermeta table joining with wp_users to list users with roles at contributor level or higher.Affected if There is at least one user with contributor, author, editor, or administrator role while the vulnerable plugin version is active.
Your environment is affected if the Restaurant Menu by MotoPress plugin is installed, active, and running version 2.4.10 or below, with at least one user account having contributor-level privileges or higher.
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 dataUpdate Restaurant Menu by MotoPress to version 2.4.11 or later. If no update is available, disable the plugin until a patched version is released.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57644 — 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-2026-57644 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