Customer data theft via unchecked OAuth provider binding
Published Jul 14, 2026 · Updated Jul 14, 2026
Authorization bypass in Easy!Appointments before 1.6.0 allows remote authenticated users to rebind another provider's Google sync. Google::oauth stores a URL-supplied provider_id in the session, and oauth_callback writes the issued token to that provider without checking ownership. A backend login and configured Google Calendar integration are required; successful rebinding exposes appointment names and email addresses and permits appointment changes.
Summary
What happened
Authorization bypass in Easy!Appointments before 1.6.0 allows remote authenticated users to rebind another provider's Google sync. Google::oauth stores a URL-supplied provider_id in the session, and oauth_callback writes the issued token to that provider without checking ownership. A backend login and configured Google Calendar integration are required; successful rebinding exposes appointment names and email addresses and permits appointment changes.
The record
- CVE
- CVE-2026-52841
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Easy Appointments
- Product
- Easy Appointments
- Classifications
- CWE-639, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-8hm4-r66f-29wr proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo