CVE-2026-48077: OpenReception: GET appointment by ID returns full appointment record without authorization
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.1.0, the GET handler at /api/tenants/{id}/appointments/{appointmentId} performs no authorization check before returning the appointment record. Any party who knows or obtains a valid appointment UUID receives the full row, including channel and agent IDs, time and timezone, status, and the AES-GCM ciphertext components (encryptedPayload, iv, authTag, dataKey). The same file's DELETE handler calls checkPermission(locals, tenantId, true) before allowing deletion. The intent is clear: appointment records are tenant-scoped and require authentication to access. The GET handler is missing the equivalent call. The middleware chain (apiAuthHandle, authGuard) does not compensate: API paths bypass authGuard entirely, and apiAuthHandle does not block requests to non-admin paths when no token is present. Version 1.1.0 patches the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenReception appointment booking softwareto a version that resolves this vulnerability.Fixed in 1.1.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-48077?
CVE-2026-48077 has a medium severity rating of 5.3.
How do I fix CVE-2026-48077?
To fix CVE-2026-48077, update to version 1.1.0 or later of OpenReception's appointment booking software.
What does CVE-2026-48077 affect?
CVE-2026-48077 affects the appointment booking software provided by OpenReception prior to version 1.1.0.
What kind of vulnerability is CVE-2026-48077?
CVE-2026-48077 is an authorization vulnerability that allows unauthorized access to appointment records.
What is the potential impact of CVE-2026-48077?
The potential impact of CVE-2026-48077 includes exposure of sensitive appointment details to unauthorized users.