CVE-2023-3288 is a high severity (CVSS 8.5) broken object level authorization flaw in Easy!Appointments. A low privileged user can call the POST /providers endpoint to create a privileged provider account. The record lists no fixed version, so check the project releases and update.
What's affected
The NVD record describes a BOLA vulnerability in the POST /providers endpoint of Easy!Appointments. A low privileged user can create a privileged user of the provider type, which is a privilege escalation inside the booking system.
The record names easyappointments:easyappointments with no version range. Its only reference is the project repository, and the page we read had no advisory or fixed version. We therefore do not state one. Treat your installed version as unknown until you compare it with the project release notes.
This is a sibling of CVE-2023-3287, which covers the admins endpoint and scores higher at 9.9. Both come from the same missing authorization pattern, so review them together.
How to check if you're exposed
Identify the version of each instance you run, then compare it with the project releases page.
Review the provider list for accounts you did not create. Providers can manage their own calendars and customer appointments, so an unexpected provider account deserves a look.
Search access logs for POST requests to the providers path made by low privileged sessions. A legitimate flow should only come from accounts that manage staff.
If you expose the API to the internet, consider limiting administrative paths to your office or VPN ranges until you have upgraded.
What to do now
- Inventory all Easy!Appointments deployments.
- Upgrade to a release that the project documents as fixing the authorization issue, once you have confirmed which one.
- Audit provider and administrator accounts and remove those you cannot explain.
- Reset credentials for accounts that were created or changed during the exposure window.
- Add authorization tests for every create, update and delete endpoint to your review checklist.
Why it matters
The weakness is CWE-639, authorization bypass through a user controlled key. The server receives a request from a signed in account and acts on it without asking whether that account may create a provider.
The score is lower than the admin variant because the created role has fewer rights, but a provider account is still an account you did not intend to create inside your booking system. The record does not claim exploitation and the CVE is not in the CISA KEV catalog. As with the sibling issue, the cheapest defence is a test that tries every privileged call with a low privileged token.
Quick check
How is this different from CVE-2023-3287?
Same weakness class, different endpoint. This one creates a provider, the other creates an administrator, which is why it scores 9.9 rather than 8.5.
Sources
Last reviewed: 19 October 2026.