CVE-2026-106000: Booking Package WordPress plugin payment bypass

CVE-2026-106000 · Severity: info · Published 2026-11-04

The Booking Package WordPress plugin, which manages appointment bookings and payments, fails to verify that customers have completed payment before confirming reservations. An attacker can create confirmed bookings without paying, allowing them to reserve services or resources for free and potentially disrupt business operations.

Technologies: Booking Package. Vendors: Booking Package.

Quick answers

Is CVE-2026-106000 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-106000 being exploited in the wild.
How severe is CVE-2026-106000?
Informational severity, published 4 November 2026.
Which products and versions are affected?
Booking Package before 1.7.34.
Is there a fix for CVE-2026-106000?
Yes: fixed in 1.7.34. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-106000 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-106000?
Check whether you run Booking Package at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 1.7.34

Technical details

The plugin does not enforce payment completion before persisting bookings to calendars configured to require online payment. This broken access control vulnerability (CWE-284) allows unauthenticated attackers to create confirmed bookings via direct API calls or form manipulation without authentication or prior payment processing, bypassing the intended payment workflow.

Affected products

  • Booking Package Booking Package before 1.7.34

Timeline

  • 2026-11-02: disclosed
  • 2026-11-04: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.