CVE-2026-48088

Name of the Vulnerable Software and Affected Versions OpenReception versions prior to 1.0.4

Description An authentication bypass exists in the appointment booking platform that allows unauthenticated network attackers to register themselves as encryption recipients for any tenant's future patient appointments. The issue occurs at the POST /api/tenants/{tenantId}/staff/{staffId}/crypto endpoint, which accepts and stores attacker-controlled ML-KEM-768 public keys without proper authentication.

One variant of the flaw allows the storage of keys despite logging an unauthorized attempt. A second variant suppresses this warning entirely when the email field is omitted from the request body and no registration cookie is present, causing a logic error where undefined === undefined evaluates to true. Additionally, the staff crypto table lacks a unique constraint on user id, allowing multiple attacker rows to coexist. Weak schema validation for passkeyId, publicKey, and privateKeyShare further allows malformed entries to be stored, which can disrupt legitimate booking flows.

Attackers can exploit this by using the GET /api/tenants/{id}/appointments/staff-public-keys endpoint to retrieve their injected keys. Since new appointments encrypt tunnel keys for all listed recipients using ML-KEM (a post-quantum key encapsulation mechanism), the attacker can decapsulate the tunnel key and decrypt all appointment payloads.

Recommendations Update OpenReception to version 1.0.4. As a temporary mitigation, restrict access to the POST /api/tenants/{tenantId}/staff/{staffId}/crypto endpoint.