CVE-2026-14311

Booking for Appointments and Events Calendar – Amelia (Premium) <= 2.4.4 - Authenticated (Custom+) Missing Authorization to Limited Account Takeover

Strategic Overview

Status
Patched in 2.4.5
Affected Version
<= 2.4.4
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-14311
View all Booking for Appointments and Events Calendar – Amelia vulnerabilities

At a glance

CVE-2026-14311 is a medium-severity Missing Authorization vulnerability in the Booking for Appointments and Events Calendar WordPress plugin, affecting versions <= 2.4.4. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom level or above. The issue is fixed in version 2.4.5; sites on affected versions should update now. Disclosed September 2026, reported by Jonah Burgess (CryptoCat).

Vulnerability Overview

The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing ownership verification on /users/customers/<id> endpoint in all versions up to, and including, 2.4.4. This makes it possible for authenticated attackers, with wpamelia-provider role, to view and modify arbitrary customers, including password reset. Takeover of WordPress user accounts, with the roles up to Editor, is also possible if that user had made an Amelia booking. This vulnerability affects only the Premium version of the plugin, where the Employee Panel is present.

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 for Appointments and Events Calendar <= 2.4.4 takes an account at Custom 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 Booking for Appointments and Events Calendar the fix is 2.4.5: builds <= 2.4.4 are affected, anything from 2.4.5 onward is not.

Remediation

Update to version 2.4.5, 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 for Appointments and Events Calendar 2.4.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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