CVE-2023-36510
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 Reservation Diary ReDi Restaurant Reservation allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ReDi Restaurant Reservation: from n/a through 23.0211.
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 confidenceThis is a Missing Authorization (Broken Access Control) vulnerability in the ReDi Restaurant Reservation plugin. The vulnerability allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthorized access to reservation data, customer information, or administrative functions without proper authentication or authorization checks. The issue affects all versions up to and including 23.0211.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Locate the ReDi Restaurant Reservation plugin installationCheck your WordPress plugins directory (wp-content/plugins/redi-restaurant-reservation) or navigate to Plugins > Installed Plugins in the WordPress admin dashboard to confirm the plugin is presentAffected if The plugin directory or listing exists on the system
-
Identify the installed plugin versionOpen the main plugin file (redi-restaurant-reservation.php) and locate the version constant in the plugin header comments, or check the version displayed in the WordPress plugins listAffected if The version number returned is 23.0211 or any earlier version
-
Verify access control on reservation endpointsAttempt to access the reservation API endpoints (typically at /wp-json/redi-api/ or similar) without providing authentication credentials or valid nonce tokensAffected if The endpoint returns reservation data, customer information, or administrative functionality without requiring login or proper capability checks
-
Inspect plugin code for capability checksReview the main plugin PHP files for missing current_user_can(), is_user_logged_in(), or nonce verification calls before executing sensitive operations such as data retrieval, modification, or deletionAffected if Sensitive functions lack authorization checks or rely solely on superficial validation that can be bypassed
A user is affected if the ReDi Restaurant Reservation plugin is installed with version 23.0211 or lower AND sensitive endpoints or functions are accessible without authentication or proper capability verification.
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 the ReDi Restaurant Reservation plugin to the latest version beyond 23.0211 to obtain the patched release. Additionally, review and enforce proper role-based access control (RBAC) checks on all sensitive endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36510 — 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-2023-36510 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