Amelia <= 1.2.16 - Unauthenticated Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 1.2.17
- Affected Plugin
- Booking for Appointments and Events Calendar – Amelia
- Affected Version
<= 1.2.16- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-26965
At a glance
CVE-2025-26965 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Booking for Appointments and Events Calendar WordPress plugin, affecting versions <= 1.2.16. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.17; sites on affected versions should update now. Disclosed February 2025, reported by Revan Arifio.
Vulnerability Overview
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, 1.2.16 due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to perform an unauthorized action.
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-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Booking for Appointments and Events Calendar <= 1.2.16 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Booking for Appointments and Events Calendar the fix is 1.2.17: builds <= 1.2.16 are affected, anything from 1.2.17 onward is not.
Remediation
Update to version 1.2.17, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Booking for Appointments and Events Calendar 1.2.17 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Booking for Appointments and Events Calendar – Amelia
- 9.8CVE-2026-9055: Booking for Appointments… Privilege Escalation
CVE-2026-9055 - 8.8CVE-2026-48889: Booking for Appointments… Privilege Escalation
CVE-2026-48889 - 8.8CVE-2026-2931: Amelia Booking 8.3 - 9.1.2 IDOR
CVE-2026-2931 - 8.8CVE-2026-24963: Booking for Appointments… Privilege Escalation
CVE-2026-24963 - 8.8CVE-2022-0687: Appointment and Event… Arbitrary File Upload
CVE-2022-0687 - 7.5CVE-2026-57702: Booking for Appointments and Events… SQL Injection
CVE-2026-57702 - 7.5CVE-2025-12482: Booking for Appointments and Events… SQL Injection
CVE-2025-12482 - 7.2CVE-2026-6286: Booking for Appointments and Events Calendar Stored XSS
CVE-2026-6286
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C