Easy!Appointments is a self hosted appointment scheduler. In versions up to and including 1.5.2, the booking reschedule view at /index.php/booking/reschedule/{appointment_hash} (handled by Booking::index()) embeds the entire customer record as inline JavaScript (const vars = {... "customer_data": {...}, ...}) without authentication and without field whitelisting. Anyone in possession of the 12-character appointment_hash — which appears in plain text in reschedule emails, confirmation page URLs, and operator-side calendar links — can read every column of that customer's row in the ea_users table. Version 1.6.0 contains a patch.
CVE-2026-52837
MEDIUMPre-NVD 6.96.9Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.9 under a secondary CVSS source (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).
Triggered by: NVD CVSS baseline
Sources: secondary
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.9Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.9
- EG Score
- 6.9(low)
- EPSS
- 27.5%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 14, 2026
Advisory Details (2)
Auto-updated Jul 14, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available
Unauthenticated customer PII disclosure on booking reschedule page · Advisory · alextselegidis/easyappointments · GitHub
https://github.com/alextselegidis/easyappointments/security/advisories/GHSA-xgr6-pqjv-3pf8github_commit Patch Available
commit 629a0415f54f (alextselegidis/easyappointments)
Patch available: alextselegidis/easyappointments 1.6.0 (contains commit 629a0415f54f)
https://github.com/alextselegidis/easyappointments/commit/629a0415f54f75556c17f4f5d9c77fda1fdbdeaeWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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-15 16:37 UTCEG score recompute
- 2026-07-14 15:06 UTCEG score recompute
- 2026-07-14 15:05 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-200
Frequently asked(5)
What is CVE-2026-52837?
CVE-2026-52837 is a medium vulnerability published on July 14, 2026. Easy!Appointments is a self hosted appointment scheduler. In versions up to and including 1.5.2, the booking reschedule view at /index.php/booking/reschedule/{appointmenthash} (handled by Booking::index()) embeds the entire customer record as inline JavaScript (const vars = {... "customerdata":…
When was CVE-2026-52837 disclosed?
CVE-2026-52837 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52837 actively exploited?
CVE-2026-52837 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52837?
CVE-2026-52837 has a CVSS v3 base score of 6.9 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-52837?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52837, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-52837
Is Your Infrastructure Affected by CVE-2026-52837?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.