CVE-2026-77705

Booking for Appointments and Events Calendar – Amelia < 2.4.10 - Authenticated (Custom Role+) Privilege Escalation

2026-09-14 00:00
Karthik Ramakrishnan

Strategic Overview

Status
Patched in 2.4.10
Affected Version
< 2.4.10
CVSS
6.3Medium
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-77705
View all Booking for Appointments and Events Calendar – Amelia vulnerabilities

At a glance

CVE-2026-77705 is a medium-severity Improper Privilege Management vulnerability in the Booking for Appointments and Events Calendar WordPress plugin, affecting versions < 2.4.10. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom Role level or above. The issue is fixed in version 2.4.10; sites on affected versions should update now. Disclosed September 2026, reported by Karthik Ramakrishnan.

Vulnerability Overview

The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Privilege Escalation in all versions up to 2.4.10. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for authenticated attackers, with custom role-level access and above, to elevate their privileges beyond those intended for their role.

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-269: Improper Privilege Management

Reaching this weakness in Booking for Appointments and Events Calendar < 2.4.10 takes an account at Custom Role 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.10: builds < 2.4.10 are affected, anything from 2.4.10 onward is not.

Remediation

Update to version 2.4.10, 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.10 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