Booking Package Plugin Vulnerability (CVE-2026-103423)

On this page

Security Alert Summary

The Booking Package plugin for WordPress contains an authorization bypass that allows unauthenticated visitors to retrieve personally identifiable information for booked customers. The plugin exposes a nominal nonce in a public JavaScript object on pages rendering the [booking_package] shortcode or widget, which can be harvested and does not provide an effective authentication barrier.


CVE Details

  • CVE ID: CVE-2026-103423
  • Affected component: Booking Package plugin for WordPress
  • Affected versions: All versions up to and including 1.7.29
  • Published: October 14, 2026 at 02:16:54 AM UTC
  • Last modified: October 14, 2026 at 02:26:59 PM UTC
  • CVSS v3.1: Base score 7.5 – HIGH – Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • Authentication / Privileges / User interaction: No authentication required; Privileges Required: NONE; User Interaction: NONE
  • Primary impact: Confidentiality: HIGH; Integrity: NONE; Availability: NONE
  • Weakness (CWE): CWE-862

Technical Details

The plugin fails to properly verify that a requester is authorized to perform an action, resulting in an authorization bypass. The vulnerable endpoint allows retrieval of records from the booking_package_booked_customers table. The nonce intended to protect the endpoint is emitted as a public CSRF token in the localized booking_package JavaScript object on any page that renders the [booking_package] shortcode or widget. Because this token is exposed to any visitor on those pages, unauthenticated attackers can harvest it and use it to access the endpoint without valid authorization checks.

Data exposed by successful requests includes personally identifiable information such as customer names, email addresses, phone numbers, physical addresses, and cancellation tokens. The issue exists due to missing or insufficient authorization checks around the endpoint that serves booked customer data.


How This Could Impact Your Website

On a site using the Booking Package plugin, an external visitor could harvest the public nonce from pages that include the plugin shortcode or widget and then query the vulnerable endpoint to retrieve booked customer records. In a typical organization this could affect multiple users: the site owner may not be aware that customer contact details are exposed, internal staff processing bookings may have confidential customer data disclosed, and external contractors or contributors with access to public pages could inadvertently reveal tokens or links tied to bookings.

Practical consequences include exposure of customer email addresses and phone numbers, which increases the risk of targeted phishing or social engineering against customers or staff. Cancellation tokens or other booking-related tokens being exposed could allow attackers to manipulate or probe booking workflows in ways that do not necessarily alter data integrity or availability but do compromise confidentiality.

If youre unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor-level accounts and other low-privilege roles that can access pages rendering the plugin shortcode or widget.
  • Enforce strong passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins to reduce attack surface.
  • Monitor site activity and access logs for unusual behavior or requests targeting booking endpoints.

If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References