Is Booking Package safe?

No known vulnerability affects the current version (1.7.44). 19 issues were found in earlier versions and fixed, the latest disclosed on Oct 28, 2026.

Checked 2 days ago against the WPVulnerability database, for version 1.7.44.

How it’s looked after

Last release: Nov 5, 2026 (4 days ago)
Releases in the last year: 46
Tested up to: WordPress 7.1.4
Support resolved: 11 of 18 threads in two months
Active installs: 10K+

19 known vulnerabilities

8 high
4 medium
7 not rated

None affects the current version.

Disclosed each year

20211
20221
20232
20241
20251
202613

Every known vulnerability in Booking Package

Newest first, with any that affect the current version at the top.

Unauthenticated Free Confirmed Booking Creation
Fixed in 1.7.34 · CVE-2026-106000 · Oct 28, 2026 · Wordfence
Missing Authorization
Fixed in 1.7.33 · CVE-2026-105997 · Oct 21, 2026 · Wordfence
Missing Authorization
Fixed in 1.7.31 · CVE-2026-105998 · Oct 21, 2026 · Wordfence
Unauthenticated Information Exposure
Fixed in 1.7.31 · CVE-2026-105999 · Oct 21, 2026 · Wordfence
Unauthenticated Information Exposure
Fixed in 1.7.31 · CVE-2026-105996 · Oct 19, 2026 · Wordfence
high
Missing Authorization to Unauthenticated Sensitive Information Disclosure via 'mode=sendBooking' with nonexistent 'timeKey' and 'public=0'
Fixed in 1.7.30 · CVE-2026-103423 · Oct 13, 2026 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via 'id' Shortcode Attribute
Fixed in 1.7.30 · CVE-2026-103425 · Oct 13, 2026 · Wordfence
Exposure of Sensitive Information to an Unauthorized Actor
Fixed in 1.7.30 · CVE-2026-105995 · Oct 10, 2026 · CVE
Unauthenticated Price Manipulation
Fixed in 1.7.25 · CVE-2026-16986 · Jul 10, 2026 · Wordfence
high
Unauthenticated SQL Injection via 'email' Form Parameter
Fixed in 1.7.21 · CVE-2026-15335 · Jun 5, 2026 · Wordfence
high
Authenticated (Editor+) Privilege Escalation via Account Takeover to updateUser AJAX Action
Fixed in 1.7.17 · CVE-2026-9851 · Jun 5, 2026 · Wordfence
medium
Unauthenticated Price Manipulation via 'amount' Parameter
Fixed in 1.7.07 · CVE-2026-4911 · Apr 27, 2026 · Wordfence
high
Missing Authorization
Fixed in 1.7.07 · CVE-2026-40774 · Apr 21, 2026 · Wordfence
medium
Reflected Cross-Site Scripting via Locale Parameter
Fixed in 1.6.73 · CVE-2024-13508 · Feb 18, 2025 · Wordfence
high
Unauthenticated Price Manipulation
Fixed in 1.6.29 · CVE-2024-30516 · Mar 28, 2024 · Wordfence
high
Reflected Cross-Site Scripting via 'mode'
Fixed in 1.6.02 · CVE-2023-39918 · Aug 7, 2023 · Wordfence
high
Authorization Bypass to Arbitrary Password Reset
Fixed in 1.5.99 · CVE-2023-37389 · Jul 5, 2023 · Wordfence
high
Unauthenticated Sensitive Data Disclosure
Fixed in 1.5.29 · CVE-2022-0709 · Mar 9, 2022 · Wordfence
medium
Reflected Cross-Site Scripting
Fixed in 1.5.11 · CVE-2021-20840 · Nov 10, 2021 · Wordfence

Questions about Booking Package’s security

Is Booking Package safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Booking Package updated: most attacks target sites that haven’t updated.

Does Booking Package have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 19 older issues, fixed in earlier versions, so keep Booking Package up to date.

Is Booking Package still maintained?

Yes. Its last release was 4 days ago. Its authors resolved 11 of the 18 support threads opened in the last two months.

Is Booking Package compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.