CVE-2026-54835
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 · uneditedUnauthenticated Broken Access Control in Five Star Restaurant Menu <= 2.5.2 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 · moderate confidenceUnauthenticated Broken Access Control vulnerability in the Five Star Restaurant Menu WordPress plugin (versions 2.5.2 and below) allows unauthenticated attackers to access functionality or data that should require proper authorization. The CVSS 7.5 score indicates network-exploitable, low-complexity access to sensitive operations without credentials.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Verify the plugin is installedNavigate to WordPress Admin > Plugins and locate 'Five Star Restaurant Menu' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn WordPress Admin > Plugins, click on 'Five Star Restaurant Menu' to view the plugin details, or inspect the plugin main PHP file header for the 'Version' fieldAffected if The version displayed is 2.5.2 or any version below 2.5.2
-
Confirm the plugin is activeIn WordPress Admin > Plugins, verify the plugin status shows 'Active' under the Five Star Restaurant Menu pluginAffected if The plugin is active and running on the site
-
Test for unauthenticated access to admin functionalityAttempt to access common admin AJAX endpoints or plugin-specific URLs without logging in (e.g., wp-admin/admin-ajax.php?action=frmsev_... or similar plugin-specific routes) using a curl request or browserAffected if The server returns data or performs actions without requiring login credentials (HTTP 200 instead of redirect to login or 403)
If the Five Star Restaurant Menu plugin is installed, active, and running version 2.5.2 or below, the environment is affected by this unauthenticated broken access control vulnerability.
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 Five Star Restaurant Menu plugin to the latest version immediately. If no patched version exists, disable the plugin until a fix is available or implement additional access controls at the web application firewall level.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54835 — 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-54835 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