Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Easy!Appointments versions before 1.6.0 let an authenticated provider create appointments in another provider's schedule through the store endpoint, or move an existing appointment into another provider's calendar through the update endpoint, because provider ownership is not checked. An attacker needs a provider account on the application. The store path also commits the foreign appointment to the database before returning a 500 error. Upgrade to Easy!Appointments 1.6.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 3.3 | Low | 3.1 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0018, the 7th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-w8xc-8g92-v77h
- OSV: GHSA-w8xc-8g92-v77h
- github.com/alextselegidis/easyappointments/security/advisories/GHSA-w8xc-8g92-v77h
- nvd.nist.gov/vuln/detail/CVE-2026-52839
- github.com/alextselegidis/easyappointments/commit/725eafa647308846ce887657db12771a829e42ef
- github.com/alextselegidis/easyappointments
- github.com/alextselegidis/easyappointments/releases/tag/1.6.0