---
id: CVE-2026-48071
title: >-
  OpenReception's appointment booking software provides an end-to-end encrypted
  appointment booking platform
summary: >-
  OpenReception's appointment booking software provides an end-to-end encrypted
  appointment booking platform. Prior to version 1.0.4, the PIN-type challenge
  throttle uses `emailHash` as the only key. The throttle rows live in the
  central `…
severity: medium
cvss: 5.8
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L'
cwe:
  - CWE-307
published: '2026-08-06'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T20:51:43.490'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-48071'
references:
  - url: >-
      https://github.com/open-reception/appointment-booking-software/commit/828b5297dc4c9827f7a43841d0f839c21462185d
    label: security-advisories@github.com
  - url: >-
      https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-f778-wf9x-3qf9
    label: security-advisories@github.com
  - url: >-
      https://github.com/open-reception/appointment-booking-software/security/advisories/GHSA-f778-wf9x-3qf9
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
epss: 0.00396
epssPercentile: 0.30982
ingestedAt: '2026-08-09T00:31:24.838Z'
---

## Overview

OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.4, the PIN-type challenge throttle uses `emailHash` as the only key. The throttle rows live in the central `challenge_throttle` table, which is shared across all tenants. Every tenant's `/api/tenants/{id}/appointments/verify-challenge` endpoint increments the same row when a PIN response fails, and every tenant's `/api/tenants/{id}/appointments/challenge` endpoint reads the same row when deciding whether to issue a new challenge. When the same `emailHash` exists in multiple tenants on the same OpenReception instance (the same patient holding tunnels in two different clinics that share the platform), an attacker who knows the patient's email can lock out that patient on tenant B by issuing failed challenge responses against tenant A. The attacker needs no relationship to tenant B; the lockout propagates through the shared throttle row. The lockout escalates with repeated failures. The first lockout triggers at 4 failed attempts and lasts approximately 60 seconds. Subsequent failures escalate the lockout duration to 5 minutes, 30 minutes, and 60 minutes per the throttle service's escalation logic. Repeated bursts produce sustained denial of service against the targeted email. Version 1.0.4 patches the issue.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.