CVE-2025-14982

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

2026-01-15 16:11
shark3y

Strategic Overview

Status
Patched in 10.14.12
Affected Plugin
Booking Calendar
Affected Version
<= 10.14.11
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-14982
View all Booking Calendar vulnerabilities

At a glance

CVE-2025-14982 is a medium-severity Missing Authorization vulnerability in the Booking Calendar WordPress plugin, affecting versions <= 10.14.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 10.14.12; sites on affected versions should update now. Disclosed January 2026, reported by shark3y.

Vulnerability Overview

The Booking Calendar plugin for WordPress is vulnerable to Missing Authorization leading to Sensitive Information Exposure in all versions up to, and including, 10.14.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view all booking records in the database, including personally identifiable information (PII) such as names, email addresses, phone numbers, physical addresses, payment status, booking costs, and booking hashes belonging to other users.

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.

CWE-862: Missing Authorization

Reaching this weakness in Booking Calendar <= 10.14.11 takes a caller who can reach the endpoint. 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 Booking Calendar the fix is 10.14.12: builds <= 10.14.11 are affected, anything from 10.14.12 onward is not.

Remediation

Update to version 10.14.12, 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: Booking Calendar 10.14.12 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14982https://www.wordfence.com/threat-intel/vulnerabilities/id/161d92e3-d255-4967-9449-be263a46bec8https://nvd.nist.gov/vuln/detail/CVE-2025-14982

Related records

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