WordPress plugin · Updated daily · Source: Wordfence Intelligence

Booking Calendar vulnerabilities: affected versions and fixes

Booking Calendar has 40,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Booking Calendar at a glance

  • 39 publicly disclosed vulnerabilities, 9 of them rated High or Critical. The most recent was disclosed on Nov 20, 2026.
  • Ranked #802 by popularity on WordPress.org (40,000+ active installs).
  • The latest version is 12.0.1 (released Nov 19, 2026). The most recent security fix shipped in 12.0.1.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Booking Calendar version

Enter the Booking Calendar version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Booking Calendar”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Booking Calendar”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (12.0.1). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Booking Calendar vulnerabilities (latest 25 of 39)

  • Booking Calendar <= 12.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'options' Shortcode Attribute

    Cross-site scripting (XSS) · CVE-2026-132781

    Affected versions: ≤ 12.0

    Fixed in: 12.0.1

    Severity: Medium 6.4 · Disclosed Nov 20, 2026

  • Booking Calendar <= 11.4.3 - Unauthenticated Sensitive Information Exposure in 'WPBC_FLEXTIMELINE_NAV' AJAX Action

    Information disclosure · CVE-2026-18496

    Affected versions: ≤ 11.4.3

    Fixed in: 11.5

    Severity: Medium 5.3 · Disclosed Oct 9, 2026

  • Booking Calendar 10.15 - 11.8.2 - Authenticated (Editor+) Information Exposure

    Information disclosure · CVE-2026-105195

    Affected versions: ≥ 10.15, ≤ 11.8.2

    Fixed in: 11.8.3

    Severity: Low 2.7 · Disclosed Oct 8, 2026

  • Booking Calendar < 11.8 - Unauthenticated Information Exposure

    Information disclosure · CVE-2026-105193

    Affected versions: < 11.8

    Fixed in: 11.8

    Severity: Medium 5.3 · Disclosed Oct 8, 2026

  • Booking Calendar <= 11.8.4 - Unauthenticated Duplicate Slot Booking

    Other weakness · CVE-2026-39601

    Affected versions: ≤ 11.8.4

    Fixed in: 11.9

    Severity: Medium 5.3 · Disclosed Oct 2, 2026

  • Booking Calendar <= 11.8.3 - Reflected Cross-Site Scripting via 'wpbc_auto_fill' Parameter

    Cross-site scripting (XSS) · CVE-2026-93655

    Affected versions: ≤ 11.8.3

    Fixed in: 11.8.4

    Severity: Medium 6.1 · Disclosed Sep 21, 2026

  • Booking Calendar <= 11.8.2 - Authenticated (Editor+) Privilege Escalation to 'data_name' Parameter

    Privilege escalation · CVE-2026-92619

    Affected versions: ≤ 11.8.2

    Fixed in: 11.8.3

    Severity: High 7.2 · Disclosed Sep 17, 2026

  • Booking Calendar <= 11.8.2 - Reflected Cross-Site Scripting via 'options' Parameter

    Cross-site scripting (XSS) · CVE-2026-92561

    Affected versions: ≤ 11.8.2

    Fixed in: 11.8.3

    Severity: Medium 6.1 · Disclosed Sep 17, 2026

  • Booking Calendar <= 11.7 - Missing Authorization

    Missing authorization · CVE-2026-74002

    Affected versions: ≤ 11.7

    Fixed in: 11.8

    Severity: Medium 5.3 · Disclosed Sep 16, 2026

  • Booking Calendar <= 11.4.2 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-59558

    Affected versions: ≤ 11.4.2

    Fixed in: 11.4.3

    Severity: High 7.2 · Disclosed Jul 27, 2026

  • Booking Calendar <= 10.14.14 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary User Settings Modification

    Missing authorization · CVE-2026-2230

    Affected versions: ≤ 10.14.14

    Fixed in: 10.14.15

    Severity: Medium 4.3 · Disclosed Feb 17, 2026

  • Booking Calendar <= 10.14.15 - Authenticated (Editor+) SQL Injection

    SQL injection · CVE-2026-32358

    Affected versions: ≤ 10.14.15

    Fixed in: 10.14.16

    Severity: Medium 4.9 · Disclosed Feb 14, 2026

  • Booking Calendar <= 10.14.13 - Missing Authorization to Unauthenticated Booking Details Exposure

    Missing authorization · CVE-2026-1431

    Affected versions: ≤ 10.14.13

    Fixed in: 10.14.14

    Severity: Medium 5.3 · Disclosed Jan 30, 2026

  • Booking Calendar <= 10.14.11 - Missing Authorization to Sensitive Information Exposure

    Missing authorization · CVE-2025-14982

    Affected versions: ≤ 10.14.11

    Fixed in: 10.14.12

    Severity: Medium 4.3 · Disclosed Jan 15, 2026

  • Booking Calendar <= 10.14.10 - Unauthenticated Sensitive Information Exposure

    Missing authorization · CVE-2025-14146

    Affected versions: ≤ 10.14.10

    Fixed in: 10.14.11

    Severity: Medium 5.3 · Disclosed Jan 8, 2026

  • Booking Calendar <= 10.14.8 - Unauthenticated SQL Injection via dates_to_check

    SQL injection · CVE-2025-14383

    Affected versions: ≤ 10.14.8

    Fixed in: 10.14.9

    Severity: High 7.5 · Disclosed Dec 15, 2025

  • Booking Calendar <= 10.14.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via bookingcalendar Shortcode

    Cross-site scripting (XSS) · CVE-2025-12804

    Affected versions: ≤ 10.14.6

    Fixed in: 10.14.7

    Severity: Medium 6.4 · Disclosed Dec 4, 2025

  • Booking Calendar <= 10.14.7 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-64381

    Affected versions: ≤ 10.14.7

    Fixed in: 10.14.8

    Severity: Medium 6.4 · Disclosed Nov 13, 2025

  • Booking Calendar <= 10.14.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-9346

    Affected versions: ≤ 10.14.1

    Fixed in: 10.14.2

    Severity: Medium 6.4 · Disclosed Aug 27, 2025

  • Booking Calendar <= 10.11.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via wpbc Shortcode

    Cross-site scripting (XSS) · CVE-2025-4669

    Affected versions: ≤ 10.11.1

    Fixed in: 10.11.2

    Severity: Medium 6.4 · Disclosed May 16, 2025

  • WP Booking Calendar <= 10.10 - Unauthenticated Post-Confirmation Booking Manipulation

    Missing authorization · CVE-2024-13821

    Affected versions: ≤ 10.10

    Fixed in: 10.10.1

    Severity: Medium 5.3 · Disclosed Feb 11, 2025

  • Booking Calendar <= 10.9.2 - Authenticated (Contributor+) DOM-Based Stored Cross-Site Scripting via 'booking' Shortcode

    Cross-site scripting (XSS) · CVE-2024-13323

    Affected versions: ≤ 10.9.2

    Fixed in: 10.9.3

    Severity: Medium 6.4 · Disclosed Jan 13, 2025

  • WP Booking Calendar <= 10.6.4 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-10893

    Affected versions: ≤ 10.6.4

    Fixed in: 10.6.5

    Severity: Medium 4.4 · Disclosed Nov 14, 2024

  • WP Booking Calendar <= 10.6.2 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-10027

    Affected versions: ≤ 10.6.2

    Fixed in: 10.6.3

    Severity: Medium 4.4 · Disclosed Oct 17, 2024

  • WP Booking Calendar <= 10.6 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-9306

    Affected versions: ≤ 10.6

    Fixed in: 10.6.1

    Severity: Medium 4.4 · Disclosed Oct 3, 2024

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 20, 2026.

Most common weaknesses in Booking Calendar

Cross-site scripting (XSS)

18 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

SQL injection

7 issues

Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.

Missing authorization

6 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Frequently asked questions

Is Booking Calendar safe to use?

Booking Calendar is a well-known plugin with 40,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (12.0.1) and turn on automatic updates.

How do I find which version of Booking Calendar my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesBooking Calendar on WordPress.org