dbcve.org
Restaurant ReservationsWordPress extension · Nicdark

CVE-2023-51403

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to after 1.8 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Nicdark Restaurant Reservations allows Stored XSS.This issue affects Restaurant Reservations: from n/a through 1.8.

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

A stored cross-site scripting (XSS) vulnerability exists in the Nicdark Restaurant Reservations WordPress plugin. The plugin fails to properly sanitize user-supplied input in reservation fields before storing and displaying it in web pages, allowing attackers to inject malicious JavaScript code that executes in browsers of users viewing reservation data.

MitigationUpdate Restaurant Reservations to the latest version if available, or implement proper input sanitization using WordPress escaping functions (such as esc_html(), esc_attr(), and wp_kses()) on all reservation input fields and output display points.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Restaurant ReservationsWordPress extension
Affected:<= 1.8

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Verify plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'Nicdark Restaurant Reservations', and note the version number displayed. Compare this version against the affected range (version 1.8 and below).
    Affected if The installed version is 1.8 or lower.
  2. Confirm reservation functionality is active
    Check if the reservation form shortcode or widget is published on a live page by searching for 'nd_reservations' in your pages/posts or checking the plugin settings for active reservation forms.
    Affected if A reservation form is published and accepting user input.
  3. Inspect stored reservation data in database
    Access the WordPress database via phpMyAdmin or command line, locate the table storing reservation data (typically wp_options or a custom table created by the plugin), and examine entries in name, email, phone, date, time, and message fields for suspicious patterns like <script> tags, javascript: URIs, or event handler attributes.
    Affected if Any reservation records contain unsanitized HTML or JavaScript code in input fields.
  4. Review frontend reservation display
    Visit pages where reservation data is displayed (such as admin reservation management pages or frontend reservation lists), view the page source, and verify whether output properly escapes special characters using esc_html(), esc_attr(), or similar functions.
    Affected if Reservation data renders as raw HTML/JavaScript without escaping in the browser.

You are affected if the Nicdark Restaurant Reservations plugin version is 1.8 or lower and reservation data can be submitted and displayed without proper sanitization.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.8
Interim mitigation

Update Restaurant Reservations to the latest version if available, or implement proper input sanitization using WordPress escaping functions (such as esc_html(), esc_attr(), and wp_kses()) on all reservation input fields and output display points.

Recommended fix Moderate confidence

Restaurant Reservations plugin version > 1.8 (check WordPress plugin repository for latest version)

  1. 1. Check if a newer version of the Restaurant Reservations plugin by Nicdark is available in the WordPress plugin repository
  2. 2. If a version newer than 1.8 is available, review the plugin changelog to confirm the XSS vulnerability (CVE-2023-51403) has been addressed
  3. 3. Before upgrading, perform a full backup of the WordPress site including database and files
  4. 4. Test the upgrade in a staging environment if possible to verify compatibility with your theme and other plugins
  5. 5. Upgrade the Restaurant Reservations plugin to the latest available version
  6. 6. Verify the fix by testing the reservation form input fields with various payloads to confirm XSS is no longer exploitable
  7. 7. Clear any caching mechanisms after the update
Caveat Verify compatibility with your WordPress version and theme before upgrading; test in staging first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Restaurant Reservations Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51403 — 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-2023-51403 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