---
title: "CVE-2026-108123: WP Booking System – Booking Calendar - Authorization Bypass"
description: "WP Booking System – Booking Calendar plugin for WordPress <= 2.1.0.3 contains an authorization bypass caused by improper user authorization verification, letting unauthenticated attackers read stored notification emails exposing customer PII, exploit requires authenticated Subscriber-level user."
url: https://panop.io/threat-heartbeat/CVE-2026-108123/
---

# CVE-2026-108123 WP Booking System – Booking Calendar - Authorization Bypass

WP Booking System – Booking Calendar plugin for WordPress <= 2.1.0.3 contains an authorization bypass caused by improper user authorization verification, letting unauthenticated attackers read stored notification emails exposing customer PII, exploit requires authenticated Subscriber-level user.

CVSS base score 7.5 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.32% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-108123)

## Details

Type

Broken Access Control

Impact

Information Disclosure

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Published

17 October 2026

Updated

19 October 2026

Weakness

[CWE-862](https://cwe.mitre.org/data/definitions/862.html)

## Vendor fix

Update to the latest version beyond 2.1.0.3.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-108123](https://nvd.nist.gov/vuln/detail/CVE-2026-108123)
- [https://plugins.trac.wordpress.org/browser/wp-booking-system/tags/2.1.0.2/includes/base/admin/booking/functions.php#L244](https://plugins.trac.wordpress.org/browser/wp-booking-system/tags/2.1.0.2/includes/base/admin/booking/functions.php#L244)
- [https://plugins.trac.wordpress.org/browser/wp-booking-system/tags/2.1.0.2/includes/base/admin/booking/functions.php#L250](https://plugins.trac.wordpress.org/browser/wp-booking-system/tags/2.1.0.2/includes/base/admin/booking/functions.php#L250)
- [https://plugins.trac.wordpress.org/browser/wp-booking-system/tags/2.1.0.2/includes/base/admin/functions.php#L30](https://plugins.trac.wordpress.org/browser/wp-booking-system/tags/2.1.0.2/includes/base/admin/functions.php#L30)
- [https://plugins.trac.wordpress.org/browser/wp-booking-system/trunk/includes/base/admin/booking/functions.php](https://plugins.trac.wordpress.org/browser/wp-booking-system/trunk/includes/base/admin/booking/functions.php)
- [https://plugins.trac.wordpress.org/changeset/3750085/wp-booking-system/trunk/includes/base/admin/booking/functions.php](https://plugins.trac.wordpress.org/changeset/3750085/wp-booking-system/trunk/includes/base/admin/booking/functions.php)
- [https://www.wordfence.com/threat-intel/vulnerabilities/id/a86fab4a-71ec-4006-96f0-46202de2f389?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/a86fab4a-71ec-4006-96f0-46202de2f389?source=cve)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
