CVE-2026-48889

Booking for Appointments and Events Calendar – Amelia <= 2.3 - Authenticated (Subscriber+) Privilege Escalation

2026-06-02 00:00
dodoh4t

Strategic Overview

Status
Patched in 2.4
Affected Version
<= 2.3
CVSS
8.8High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-48889
View all Booking for Appointments and Events Calendar – Amelia vulnerabilities

At a glance

CVE-2026-48889 is a high-severity Improper Privilege Management vulnerability in the Booking for Appointments and Events Calendar WordPress plugin, affecting versions <= 2.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.4; sites on affected versions should update now. Disclosed June 2026, reported by dodoh4t.

Vulnerability Overview

The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to that of an administrator.

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, integrity, availability — full site compromise territory.

CWE-269: Improper Privilege Management

Reaching this weakness in Booking for Appointments and Events Calendar <= 2.3 takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Booking for Appointments and Events Calendar the fix is 2.4: builds <= 2.3 are affected, anything from 2.4 onward is not.

Remediation

Update to version 2.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: Booking for Appointments and Events Calendar 2.4 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