Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Easy!Appointments versions up to and including 1.5.2 have an authorization bypass in the Google Calendar OAuth flow. Any logged-in backend user (admin, provider, or secretary) can bind a different provider's Google sync to their own Google account, so that provider's appointments and customer names and emails are pushed into the attacker's calendar. No fixed version is listed.
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.1 | Low | 3.1 | CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0021, the 10th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 29 Jul 2026, 16:29 UTC Confirmed by GitHub Advisory Database
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8hm4-r66f-29wr
- OSV: GHSA-8hm4-r66f-29wr
- github.com/alextselegidis/easyappointments/security/advisories/GHSA-8hm4-r66f-29wr
- nvd.nist.gov/vuln/detail/CVE-2026-52841
- github.com/alextselegidis/easyappointments/commit/4b2d245d2cd2058dc76e05f6eb65b26699268471
- github.com/alextselegidis/easyappointments
- github.com/alextselegidis/easyappointments/releases/tag/1.6.0