CVE-2024-38737
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 Accessing Functionality Not Properly Constrained by ACLs.This issue affects ReDi Restaurant Reservation: from n/a through 24.0422.
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 confidenceThe ReDi Restaurant Reservation WordPress plugin versions through 24.0422 lacks proper authorization checks, allowing authenticated users (with low-level privileges like subscriber) to access reservation management functions that should be restricted to administrators only.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Identify ReDi Restaurant Reservation plugin versionIn WordPress admin dashboard, go to Plugins > Installed Plugins and locate 'ReDi Restaurant Reservation'. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment block.Affected if The installed version is 24.0422 or any version number lower than 24.0422 (e.g., 24.0310, 23.1201, etc.)
-
Verify current WordPress user roleLog in as a user with the 'Subscriber' role (or any low-privilege role). Go to Users > All Users to confirm the role assigned to the account you are testing with.Affected if The tested account has only the Subscriber role or another low-privilege role that should not have access to reservation management.
-
Test access to reservation management functionsUsing a low-privilege (Subscriber) account, attempt to access the reservation management dashboard or admin pages of ReDi Restaurant Reservation (typically found under the ReDi Reservation menu in admin sidebar). Attempt actions like viewing, editing, or deleting reservations.Affected if A user with Subscriber role can view, modify, or delete reservations, or can access admin-only reservation management pages without receiving an 'insufficient privileges' error.
You are affected if the plugin version is 24.0422 or lower AND a user with Subscriber-level permissions can access or modify reservations that should be restricted to administrators.
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 ReDi Restaurant Reservation which should include proper capability checks and nonce verification for all privileged functions.
- 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-2024-38737 — 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-2024-38737 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