CVE-2026-25327
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 · uneditedMissing Authorization vulnerability in Rustaurius Five Star Restaurant Reservations restaurant-reservations allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Five Star Restaurant Reservations: from n/a through <= 2.7.9.
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 confidenceMissing Authorization vulnerability in the Five Star Restaurant Reservations WordPress plugin allows attackers to exploit incorrectly configured access control security levels, enabling unauthorized users to perform actions they should not have privileges for.
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
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm plugin installationCheck your WordPress installation for the Five Star Restaurant Reservations plugin in wp-content/plugins/ or via WordPress admin dashboard under PluginsAffected if Plugin is installed and active
-
Identify installed versionLocate the plugin's main PHP file (typically restaurant-reservations.php) and read the version header comment, or check the version in WordPress admin plugin listAffected if Version is older than the patched release and matches publicly disclosed affected versions
-
Verify AJAX endpoint exposureInspect the plugin's includes/ajax.php or similar AJAX handler files to see if capability checks are properly implemented before processing requestsAffected if AJAX endpoints lack proper capability checks or use insufficient access control validation
-
Test authorization on sensitive functionsUse a low-privilege user account (subscriber or contributor role) to attempt actions like managing reservations, modifying settings, or accessing admin functions that should require administrator privilegesAffected if Low-privilege users can perform actions reserved for administrators
-
Review user role configurationCheck the plugin settings under Reservations > Settings > General to see if Access Control or Permission settings allow overly broad user roles to access restricted featuresAffected if Plugin configuration grants excessive permissions to non-administrator roles
Your environment is affected if the Five Star Restaurant Reservations plugin is installed with a version that matches the affected range AND unauthorized users can access administrative functions or perform privileged actions due to missing capability checks.
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 proper capability checks and authorization validation on all sensitive plugin functions and AJAX endpoints to enforce correct access control levels.
- 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-2026-25327 — 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-25327 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