Safeguard
Vulnerability Analysis•

CVE-2023-3287: Critical Privilege Escalation in Easy!Appointments

CVE-2023-3287 is a critical authorization flaw in Easy!Appointments that lets a low privileged user create an admin account. Check release notes, update.

Safeguard Security Team
3 min read

CVE-2023-3287 is a critical (CVSS 9.9) broken object level authorization flaw in Easy!Appointments. A low privileged user can call the POST /admins endpoint to create an administrator. The record gives no fixed version, so check the project releases and update.

What's affected

The NVD record describes a BOLA vulnerability in the POST /admins endpoint of Easy!Appointments. A user with low privileges can create a high privileged user, which is a direct privilege escalation to administrator.

The record lists the product as easyappointments:easyappointments with no version range, and its only reference is the project repository on GitHub. We read that page and it carried no security advisory or fixed version, so we cannot state one. Check the project release notes and your installed version before you rely on any assumption.

A sibling record, CVE-2023-3288, describes the same pattern on the providers endpoint with a lower score. If you run Easy!Appointments, handle both together.

How to check if you're exposed

Find the version you run. In a self hosted install the version appears in the admin footer or in the application configuration, and your deployment method may record it in a release tag or image tag.

Then look for evidence of misuse. Review the user table for administrator accounts you did not create, and compare creation times with your real onboarding events.

Review application and web server logs for POST requests to the admins endpoint from accounts that should not manage administrators.

If the booking system sits behind a reverse proxy, you can also restrict who may reach administrative API paths while you wait to upgrade.

What to do now

  1. List every Easy!Appointments instance you operate, including test and staging copies.
  2. Check the project repository releases for a version that addresses the API authorization issue and plan the upgrade.
  3. Audit the administrators and providers lists now and remove any account you cannot account for.
  4. Reset passwords and any API tokens for administrator accounts you do keep if misuse is possible.
  5. Restrict access to administrative paths by network where you can, as a stopgap.

Why it matters

The weakness is CWE-639, authorization bypass through a user controlled key. In plain terms, the endpoint accepts a request from a signed in user without checking that this user is allowed to create administrators. API specific authorization bugs like this are common because each endpoint needs its own check.

The impact is high because an admin account controls every booking, customer record and setting. The record does not claim exploitation in the wild and the CVE is not in the CISA KEV catalog. Automated tests that call every endpoint with a low privileged token are the practical way to catch this class of bug before release.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does a low privileged account need to exist already?

Yes. The record says a low privileged user can create the admin, so the attacker needs some valid account first. That is why open registration or shared credentials raise the risk.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.