CVE-2026-109368

WP Booking System <= 2.1.0.3 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via wpbs_refresh_calendar_editor AJAX action

2026-10-16 14:38
Wordfence PRISM

Strategic Overview

Status
Patched in 2.1.0.4
Affected Plugin
WP Booking System – Booking Calendar
Affected Version
<= 2.1.0.3
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-109368
View all WP Booking System – Booking Calendar vulnerabilities

At a glance

CVE-2026-109368 is a medium-severity Missing Authorization vulnerability in the WP Booking System WordPress plugin, affecting versions <= 2.1.0.3. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.1.0.4; sites on affected versions should update now. Disclosed October 2026, reported by Wordfence PRISM.

Vulnerability Overview

The WP Booking System – Booking Calendar plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.1.0.3 via the 'id' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract private per-event booking descriptions and booking IDs from any calendar managed by the site.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Reaching this weakness in WP Booking System <= 2.1.0.3 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Booking System the fix is 2.1.0.4: builds <= 2.1.0.3 are affected, anything from 2.1.0.4 onward is not.

Remediation

Update to version 2.1.0.4, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Booking System 2.1.0.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-109368https://www.wordfence.com/threat-intel/vulnerabilities/id/164a276a-612f-416f-b9ef-1c2e6dd0e8e4https://nvd.nist.gov/vuln/detail/CVE-2026-109368

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C