Easy!Appointments is a self hosted appointment scheduler. Versions prior to 1.6.0 correctly filter provider-scoped appointments in the appointments/search response, proving that provider isolation is an intended security boundary. However, the direct mutation endpoints appointments/store and appointments/update only check generic appointment privileges and never verify that the submitted id_users_provider belongs to the current session. A normal authenticated provider can inject new appointments into another provider's schedule via store, or reassign existing appointments into a foreign provider's calendar via update. The store path contains an additional write-before-crash bug: the unauthorized row is committed to the database before the controller crashes on a type error, so the attacker receives an error response while the foreign appointment is already persisted. Version 1.6.0 patches the issue.
CVE-2026-52839
This low-severity CVE scores 3.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.3
- EG Score
- 3.3(low)
- EPSS
- 4.2%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
References (3)
- security-advisories@githubhttps://github.com/alextselegidis/easyappointments/commit/4abb10545d83ac1a57d03f6502376ee67696ea7c
- security-advisories@githubhttps://github.com/alextselegidis/easyappointments/security/advisories/GHSA-w8xc-8g92-v77h
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/alextselegidis/easyappointments/security/advisories/GHSA-w8xc-8g92-v77h
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-14 15:42 UTCEG score recompute
- 2026-07-14 15:40 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862 · CWE-639
Frequently asked(5)
What is CVE-2026-52839?
When was CVE-2026-52839 disclosed?
Is CVE-2026-52839 actively exploited?
What is the CVSS score of CVE-2026-52839?
How do I remediate CVE-2026-52839?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-52839
Is Your Infrastructure Affected by CVE-2026-52839?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.