WordPress security changelog
HIGH CVE-2026-5465 Deferred

Booking for Appointments and Events Calendar – Amelia: Broken access control

Booking for Appointments and Events Calendar – Amelia is affected by broken access control. Exploitation requires an authenticated WordPress account. A successful request can reach data or an operation that should be restricted to another user or a more privileged role. The published affected range is <= 2.1.3.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Booking for Appointments and Events Calendar – Amelia
Plugin slug
ameliabooking
Affected
<= 2.1.3
Safe version
See mitigation notes
Published
Apr 07, 2026
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published Apr 07, 2026 and is one of 28 known issues for this plugin.

What to do

Update, patch or deactivate.

No fixed release is identified. Update Booking for Appointments and Events Calendar – Amelia when a release after 2.1.3 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 2.4.7, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.1.3. This is due to the `UpdateProviderCommandHandler` failing to validate changes to the `externalId` field when a Provider (Employee) user updates their own profile. The `externalId` maps directly to a WordPress user ID and is passed to `wp_set_password()` and `wp_update_user()` without authorization checks. This makes it possible for authenticated attackers, with Provider-level (Employee) access and above, to take over any WordPress account — including Administrator — by injecting an arbitrary `externalId` value when updating their own provider profile.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

Primary and upstream sources