Description
Easy!Appointments is a self hosted appointment scheduler. In versions prior to 1.6.0, `Google::oauth` at `application/controllers/Google.php:278` stores its URL-supplied `provider_id` in the session, and `oauth_callback` saves the issued Google OAuth token against that row without checking the caller owns the provider. Any logged-in backend user (admin, provider, or secretary) rebinds a peer provider's Google sync to a Google account they control. The peer's appointments then sync into the attacker's calendar with each customer's name and email attached as attendee data. Version 1.6.0 patches the issue.
Published: 2026-07-14
Score: 3.1 Low
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Easy!Appointments versions below 1.6.0 allow a logged‑in backend user—admin, provider, or secretary—to rebind a peer provider’s Google sync to their own Google account because the OAuth callback does not verify provider ownership. The rebind causes that provider’s appointments, along with customer names and emails, to be synced to the attacker’s calendar, exposing sensitive customer information. This is an authorization bypass that results in unauthorized data disclosure.

Affected Systems

The vulnerability affects all releases of Easy!Appointments from every vendor version prior to 1.6.0. The specific product impacted is alextselegidis:easyappointments, with the affected range being all versions less than 1.6.0.

Risk and Exploitability

The CVSS score of 3.1 marks it as low severity, and the EPSS < 1% indicates a very low exploitation probability. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires a user with backend privileges to perform a simple rebind action; no external attack vector is needed. Because the attacker can gain visibility of all appointments for a provider, the impact on confidentiality is significant, though the overall risk remains moderate due to the low likelihood of exploitation.

Generated by OpenCVE AI on July 31, 2026 at 10:06 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the Easy!Appointments 1.6.0 or newer patch that validates provider ownership before saving the OAuth token.
  • If an upgrade is delayed, revoke all existing Google sync bindings and re‑establish them only after confirming the correct provider ownership.
  • Monitor system logs for unexpected rebind activity and audit user actions involving OAuth configuration changes.

Generated by OpenCVE AI on July 31, 2026 at 10:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-8hm4-r66f-29wr Easy!Appointments: Authorization bypass in Google OAuth provider binding lets any backend user rebind a peer provider's Google sync
History

Tue, 14 Jul 2026 17:00:00 +0000

Type Values Removed Values Added
First Time appeared Alextselegidis
Alextselegidis easyappointments
Vendors & Products Alextselegidis
Alextselegidis easyappointments

Tue, 14 Jul 2026 15:45:00 +0000

Type Values Removed Values Added
Description Easy!Appointments is a self hosted appointment scheduler. In versions prior to 1.6.0, `Google::oauth` at `application/controllers/Google.php:278` stores its URL-supplied `provider_id` in the session, and `oauth_callback` saves the issued Google OAuth token against that row without checking the caller owns the provider. Any logged-in backend user (admin, provider, or secretary) rebinds a peer provider's Google sync to a Google account they control. The peer's appointments then sync into the attacker's calendar with each customer's name and email attached as attendee data. Version 1.6.0 patches the issue.
Title Easy!Appointments: Authorization bypass in Google OAuth provider binding lets any backend user rebind a peer provider's Google sync
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N'}


Subscriptions

Alextselegidis Easyappointments
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-14T15:45:45.967Z

Reserved: 2026-06-08T18:41:27.724Z

Link: CVE-2026-52841

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T10:15:06Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key