HomeWordPress vulnerabilitiesBooking Package
Booking Package vulnerabilities
Booking Package has 6 known vulnerabilities in this database. The most recent published record is dated 26 Aug 2026.
- Known vulnerabilities
- 6
- Active installs
- 10,000+
- Latest version
- 1.7.29
- Last updated
- 28 Sep 2026
- Most recent
- 26 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-16986 | Medium 5.3 | Before 1.7.25 | Fixed in 1.7.25 | 26 Aug 2026 |
| SQL injection CVE-2026-15335 | High 7.5 | Up to 1.7.20 | Fixed in a later version (latest 1.7.29) | 11 Jul 2026 |
| Privilege escalation CVE-2026-9851 | High 7.2 | Up to 1.7.16 | Fixed in a later version (latest 1.7.29) | 6 Jun 2026 |
| Security weakness CVE-2026-4911 | Medium 5.3 | Up to 1.7.06 | Fixed in a later version (latest 1.7.29) | 28 Apr 2026 |
| Cross-site scripting (XSS) CVE-2024-13508 | Medium 6.1 | Up to 1.6.72 | Fixed in a later version (latest 1.7.29) | 19 Feb 2025 |
| Sensitive data exposure CVE-2022-0709 | High 7.5 | Before 1.5.29 | Fixed in 1.5.29 | 4 Apr 2022 |
Read the published descriptions
- CVE-2026-16986, 26 Aug 2026
- The Booking Package WordPress plugin before 1.7.25 does not validate the payment amount server-side against the stored service price, deriving the expected charge from attacker-supplied request values instead, so an unauthenticated attacker can pay an arbitrary fraction of a service's real price. CVE record
- CVE-2026-15335, 11 Jul 2026
- The Booking Package plugin for WordPress is vulnerable to generic SQL Injection via 'email' Form Parameter (form<N>) in all versions up to, and including, 1.7.20 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The vulnerable REST API endpoint /wp-json/booking-package/v1/request is registered with permission_callback: __return_true and wp_magic_quotes does not apply to REST-sourced $_POST values, meaning single quotes in the payload reach the SQL sink intact without any authentication requirement. The impact of this is severely limited as the vulnerable parameter goes through is_email. CVE record
- CVE-2026-9851, 6 Jun 2026
- The Booking Package plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in versions up to, and including, 1.7.16. This is due to a missing capability check on the 'updateUser' branch of the package_app_action AJAX endpoint, where the handler only validates a nonce and the dispatcher invokes Schedule::updateUser() with the $administrator argument hard-coded to 1, bypassing the only owner-restriction check inside that function and allowing the target user to be determined solely by attacker-supplied input passed directly to wp_update_user(). This makes it possible for authenticated attackers, with Editor-level access and above, to change the email address and password of any account, including Administrator accounts, resulting in a full site takeover. CVE record
- CVE-2026-4911, 28 Apr 2026
- The Booking Package plugin for WordPress is vulnerable to Price Manipulation in versions up to, and including, 1.7.06 This is due to the intentForStripe() function passing user-controlled $_POST['amount'] directly to the Stripe PaymentIntent API without validation, and the commitStripe() function ignoring the server-calculated amount when confirming the payment. While the server correctly calculates the booking cost via getAmount() based on services, guests, taxes, and coupons, this calculated amount is never validated against or used to update the PaymentIntent because the critical code in CreditCard.php that would include the calculated amount in the PaymentIntent update is commented out. This makes it possible for unauthenticated attackers to book services at arbitrary prices (e.g., $0.01 instead of $500.00) by manipulating the amount parameter during PaymentIntent creation and completing the booking with the fraudulent payment. CVE record
- CVE-2024-13508, 19 Feb 2025
- The Booking Package plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the locale parameter in all versions up to, and including, 1.6.72 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
- CVE-2022-0709, 4 Apr 2022
- The Booking Package WordPress plugin before 1.5.29 requires a token for exporting the ical representation of it's booking calendar, but this token is returned in the json response to unauthenticated users performing a booking, leading to a sensitive data disclosure vulnerability. CVE record
What to do if you run Booking Package
If you run Booking Package, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Booking Package vulnerabilities
Free. We email you when a new vulnerability is published for Booking Package, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.