Booking for Appointments and Events Calendar – Amelia <= 1.2.19 - Unauthenticated Full Path Disclosure
Strategic Overview
- Status
- Patched in 1.2.20
- Affected Plugin
- Booking for Appointments and Events Calendar – Amelia
- Affected Version
<= 1.2.19- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-2578
At a glance
CVE-2025-2578 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Booking for Appointments and Events Calendar WordPress plugin, affecting versions <= 1.2.19. 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.20; sites on affected versions should update now. Disclosed March 2025, reported by zhuxuan wu.
Vulnerability Overview
The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.2.19 via the 'wpAmeliaApiCall' function. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Booking for Appointments and Events Calendar <= 1.2.19 carries this weakness at wpAmeliaApiCall, and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Booking for Appointments and Events Calendar the fix is 1.2.20: builds <= 1.2.19 are affected, anything from 1.2.20 onward is not.
Remediation
Update to version 1.2.20, 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.20 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 5.3CVE-2026-40789: Booking for Appointments… Information Exposure
CVE-2026-40789 - 5.3CVE-2023-49282: Amelia 1.2.18 - 1.2.36 Sensitive Information Exposure
CVE-2023-49282 - 5.3CVE-2024-6552: Booking for Appointments… Full Path Disclosure
CVE-2024-6552 - 4.3CVE-2026-14213: Booking for Appointments… Information Exposure
CVE-2026-14213
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-5465: Amelia IDOR
CVE-2026-5465 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C