dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-24529

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in Alejandro Quick Restaurant Reservations quick-restaurant-reservations allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Quick Restaurant Reservations: from n/a through <= 1.6.7.

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 confidence

Missing authorization vulnerability in the Quick Restaurant Reservations WordPress plugin allows unauthenticated or low-privilege users to access functions or data they should not be able to access. The plugin incorrectly implements access control checks, allowing exploitation of improperly configured security levels.

MitigationImplement proper capability checks and authorization verification for all sensitive functions and AJAX endpoints in the plugin, ensuring users have appropriate permissions before allowing access to reservation data or management features.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Quick Restaurant Reservations plugin is installed
    Check for the plugin directory at wp-content/plugins/quick-restaurant-reservations/ or search for 'Quick Restaurant Reservations' in the WordPress plugins admin panel
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Open the plugin's main PHP file (usually quick-restaurant-reservations.php) and look for the 'Version:' header in the file comment, or check readme.txt for the version field
    Affected if The installed version is older than the latest available version (indicating unpatched state)
  3. Test AJAX endpoint accessibility without authentication
    Send a request to wp-admin/admin-ajax.php with a Quick Restaurant Reservations action (common actions include qrr_ajax_*, qrr_*, or similar) without providing authentication cookies or WP nonce, using curl or browser dev tools
    Affected if The AJAX endpoint returns successful data or performs actions without requiring login or proper capability verification
  4. Inspect plugin code for capability checks
    Review the main plugin PHP file and any action/filter hook registrations to see if current_user_can() or similar WordPress capability checks are present before sensitive operations (managing reservations, accessing customer data, modifying settings)
    Affected if No capability checks are found before reservation data retrieval, creation, modification, or deletion functions
  5. Test low-privilege user access to admin functions
    Log in with a subscriber-level or contributor-level WordPress user account and attempt to access plugin admin pages or functions directly via URL, or call AJAX endpoints that should be restricted to administrators
    Affected if Low-privilege users can view, create, modify, or delete reservations that they should not have access to
  6. Check for unprotected reservation data exposure
    Use a web proxy or browser developer tools to examine API responses when accessing reservation-related pages; verify if reservation details (customer names, emails, phone numbers, booking details) are returned without verifying the requesting user's permissions
    Affected if Reservation data is returned to users who lack the manage_options capability or appropriate reservation management permissions

A user is affected if the Quick Restaurant Reservations plugin is installed and either the version is unpatched or unauthenticated/low-privilege users can access reservation data or management functions without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper capability checks and authorization verification for all sensitive functions and AJAX endpoints in the plugin, ensuring users have appropriate permissions before allowing access to reservation data or management features.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24529 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24529 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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