CVE-2025-54038
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 jetmonsters Restaurant Menu by MotoPress mp-restaurant-menu allows Cross Site Request Forgery.This issue affects Restaurant Menu by MotoPress: from n/a through <= 2.4.6.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the mp-restaurant-menu WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as menu modifications) by crafting malicious requests that the user's browser automatically submits due to lack of proper anti-CSRF token validation.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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.
-
Confirm the mp-restaurant-menu plugin is installedNavigate to WordPress Admin > Plugins and locate mp-restaurant-menu in the list of installed plugins. Verify if it shows as Active.Affected if The plugin is installed and active, exposing admin menu modification functions to potential CSRF attacks.
-
Identify the installed plugin versionIn the Plugins list, click on the plugin name or view details to find the version number displayed.Affected if The installed version falls within any vulnerable version range (compare your version to the affected ranges published for this CVE).
-
Inspect admin forms for anti-CSRF token presenceView page source of plugin admin pages (menu management, settings). Search for a nonce field (typically named _wpnonce, nonce, or similar) in all <form> tags that perform state-changing actions.Affected if Forms submitting menu modifications lack a valid anti-CSRF nonce field, indicating the protection is missing.
-
Check AJAX requests for nonce verificationUse browser developer tools Network tab to capture plugin AJAX requests. Inspect the request payload for a nonce parameter being sent with each state-changing AJAX call.Affected if AJAX requests modifying menu data do not include a nonce parameter, allowing forged requests.
-
Verify SameSite cookie attribute configurationIn browser developer tools Application tab, examine cookies set by the site. Check if session or authentication cookies related to the plugin have the SameSite attribute set to Lax or Strict.Affected if Cookies lack SameSite attributes, leaving them vulnerable to being sent in cross-site requests.
A defender is affected if the mp-restaurant-menu plugin is active and its version matches the vulnerable range, and inspection reveals missing nonce tokens in forms/AJAX requests or absent SameSite cookie attributes.
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) for all state-changing operations (form submissions, AJAX requests) and add SameSite cookie attributes and referer validation to prevent CSRF attacks.
- 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-2025-54038 — 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-2025-54038 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