CVE-2025-68044
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 · uneditedAuthorization Bypass Through User-Controlled Key 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.4.
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 confidenceAuthorization bypass vulnerability in the Five Star Restaurant Reservations WordPress plugin allows attackers to bypass access control checks by manipulating user-controlled keys. The plugin incorrectly uses user-supplied input as authorization keys without proper validation, enabling unauthorized access to reservation data or administrative functions.
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
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 plugin installation and activation statusIn WordPress admin, navigate to Plugins > Installed Plugins and verify the 'Five Star Restaurant Reservations' plugin is present and activeAffected if The plugin is installed and active in the WordPress environment
-
Identify installed plugin versionClick on the plugin name in the Plugins list to view the version number, or check the plugin's main PHP file header for the Version fieldAffected if Version cannot be confirmed as patched or is within an affected release range
-
Verify reservation endpoints are publicly accessibleTest the reservation submission and viewing endpoints (typically /reservation/ or similar) without providing authentication credentials to determine if they accept unauthenticated requestsAffected if Reservation endpoints process requests without requiring user authentication
-
Check access control on reservation parameter handlingSubmit reservation requests with manipulated ID parameters (such as reservation_id, user_id, or similar) to different numeric values and observe if the system returns data for reservations belonging to other usersAffected if Manipulating ID parameters in requests returns reservation data or allows actions on reservations the authenticated user does not own
If the Five Star Restaurant Reservations plugin is active and reservation access can be bypassed by manipulating user-controlled parameters, the environment is affected by this authorization bypass 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 to the latest version of Five Star Restaurant Reservations plugin and audit all endpoints that rely on key-based authorization for proper access control validation.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68044 — 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-68044 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