WordPress plugin · booking
Is Booking Calendar safe?
Safe on 11.9.1 or newer.
The current version, 11.9.1, is past every affected range on record (33 of 33 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 33
- High or critical
- 7
- Exploited
- none
- Current version
- 11.9.1
- Last updated
- Oct 11, 2026
- Active installs
- 40,000+
Every recorded flaw
- Oct 10, 2026Booking Calendar: Sensitive Information ExposureCVE-2026-18496 · affects up to 11.4.3 · reported by WordfenceMedium 5.3
- Oct 8, 2026Booking Calendar: Does not adequately restrictCVE-2026-105195 · fixed in 11.8.3 · reported by WPScanLow 2.7
- Oct 8, 2026Booking Calendar: Does not generate its per-booking access hashes with sufficient entropyCVE-2026-105193 · fixed in 11.8 · reported by WPScanMedium 4.8
- Oct 2, 2026Booking Calendar: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVE-2026-39601 · affects up to 11.8.4 · reported by PatchstackLow 3.7
- Sep 22, 2026Booking Calendar: Reflected Cross-Site ScriptingCVE-2026-93655 · affects up to 11.8.3 · reported by WordfenceMedium 6.1
- Sep 18, 2026Booking Calendar: Privilege EscalationCVE-2026-92619 · affects up to 11.8.2 · reported by WordfenceHigh 7.2
- Sep 18, 2026Booking Calendar: Reflected Cross-Site ScriptingCVE-2026-92561 · affects up to 11.8.2 · reported by WordfenceMedium 6.1
- Sep 17, 2026Unauthenticated Broken Access Control in Booking Calendar <= 11.7 versions.CVE-2026-74002 · affects up to 11.7 · reported by PatchstackMedium 5.3
- Jul 27, 2026Unauthenticated Cross Site Scripting (XSS) in Booking Calendar <= 11.4.2 versions.CVE-2026-59558 · affects up to 11.4.2 · reported by PatchstackHigh 7.1
- Mar 13, 2026Booking Calendar: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVE-2026-32358 · affects up to 10.14.15 · reported by PatchstackHigh 7.6
- Feb 18, 2026Booking Calendar: Insecure Direct Object ReferenceCVE-2026-2230 · affects up to 10.14.14 · reported by WordfenceMedium 4.3
- Jan 31, 2026Booking Calendar: Unauthorized access of dataCVE-2026-1431 · affects up to 10.14.13 · reported by WordfenceMedium 5.3
- Jan 16, 2026Booking Calendar: Missing Authorization leading to Sensitive Information ExposureCVE-2025-14982 · affects up to 10.14.11 · reported by WordfenceMedium 4.3
- Jan 9, 2026Booking Calendar: Sensitive Information ExposureCVE-2025-14146 · affects up to 10.14.10 · reported by WordfenceMedium 5.3
- Dec 15, 2025Booking Calendar: Time-based blind SQL InjectionCVE-2025-14383 · affects up to 10.14.8 · reported by WordfenceHigh 7.5
- Dec 4, 2025Booking Calendar: Stored Cross-Site ScriptingCVE-2025-12804 · affects up to 10.14.6 · reported by WordfenceMedium 6.4
- Nov 13, 2025Booking Calendar: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2025-64381 · affects up to 10.14.7 · reported by PatchstackMedium 6.5
- Aug 28, 2025Booking Calendar: Stored Cross-Site ScriptingCVE-2025-9346 · affects up to 10.14.1 · reported by WordfenceMedium 6.4
- May 17, 2025WP Booking Calendar: Stored Cross-Site ScriptingCVE-2025-4669 · affects up to 10.11.1 · reported by WordfenceMedium 6.4
- Feb 12, 2025WP Booking Calendar: Unauthenticated Post-Confirmation Booking ManipulationCVE-2024-13821 · affects up to 10.10 · reported by WordfenceMedium 5.3
- Jan 14, 2025WP Booking Calendar: Stored Cross-Site ScriptingCVE-2024-13323 · affects up to 10.9.2 · reported by WordfenceMedium 6.4
- Dec 3, 2024WP Booking Calendar: Does not sanitise and escape some of its settingsCVE-2024-10893 · fixed in 10.6.5 · reported by WPScanMedium 4.8
- Nov 7, 2024WP Booking Calendar: Does not sanitise and escape some of its Widgets settingsCVE-2024-10027 · fixed in 10.6.3 · reported by WPScanMedium 4.8
- Oct 4, 2024WP Booking Calendar: Stored Cross-Site ScriptingCVE-2024-9306 · affects up to 10.6 · reported by WordfenceMedium 4.4
- Aug 30, 2024WP Booking Calendar: Reflected Cross-Site ScriptingCVE-2024-8274 · affects up to 10.5 · reported by WordfenceMedium 6.1
- Jul 24, 2024WP Booking Calendar: Stored Cross-Site ScriptingCVE-2024-6930 · affects up to 10.2.1 · reported by WordfenceMedium 6.4
- Mar 26, 2024Booking Calendar: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVE-2023-23991 · affects up to 9.4.3 · reported by PatchstackHigh 7.6
- Feb 8, 2024WP Booking Calendar: SQL InjectionCVE-2024-1207 · affects up to 9.9 · reported by Wordfence3.2% oddsCritical 9.8
- Feb 1, 2024WP Booking Calendar: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2023-51520 · fixed in 9.7.4 · reported by PatchstackMedium 6.5
- Oct 16, 2023Booking Calendar: Does not sanitize and escape some of its booking from dataCVE-2023-4620 · fixed in 9.7.3.1 · reported by WPScanMedium 6.1
- Sep 6, 2022Cross-Site Request Forgery (CSRF) vulnerability in WPdevelop/Oplugins Booking Calendar plugin <= 9.2.1 at WordPress leading to Translations Update.CVE-2022-33177 · affects up to 9.2.1 · reported by PatchstackMedium 5.4
- May 10, 2022Booking Calendar: PHP Object InjectionCVE-2022-1463 · affects up to 9.1 · reported by Wordfence1.7% oddsHigh 8.8
- Jan 3, 2022Booking Calendar: Does not sanitise and escape the booking_type parameter before outputting it back in an admin pageCVE-2021-25040 · fixed in 8.9.2 · reported by WPScanMedium 6.1
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.