CVE-2024-6332

Booking for Appointments and Events Calendar – Amelia Premium <= 7.7 and Lite <= 1.2.4 - Missing Authorization to Sensitive Information Exposure

2024-09-04 21:24
Nadim Zubidat

Strategic Overview

Status
Patched in 1.2.5
Affected Version
<= 1.2.4
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-6332
View all Booking for Appointments and Events Calendar – Amelia vulnerabilities

At a glance

CVE-2024-6332 is a medium-severity Missing Authorization vulnerability in the Booking for Appointments and Events Calendar WordPress plugin, affecting versions <= 1.2.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.5; sites on affected versions should update now. Disclosed September 2024, reported by Nadim Zubidat.

Vulnerability Overview

The Booking for Appointments and Events Calendar – Amelia Premium and Lite plugins for WordPress are vulnerable to unauthorized access of data due to a missing capability check on the 'ameliaButtonCommand' function in all versions up to, and including, Premium 7.7 and Lite 1.2.4. This makes it possible for unauthenticated attackers to access employee calendar details, including Google Calendar OAuth tokens in the premium version.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Booking for Appointments and Events Calendar <= 1.2.4 carries this weakness at ameliaButtonCommand, and reaching it 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 for Appointments and Events Calendar the fix is 1.2.5: builds <= 1.2.4 are affected, anything from 1.2.5 onward is not.

Remediation

Update to version 1.2.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 1.2.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