CVE-2026-48076: OpenReception appointment booking unauthorized channel access

CVE-2026-48076 · Severity: medium · CVSS 6.5 · Published 2026-08-06

OpenReception's appointment booking platform allows attackers to bypass channel privacy controls and book appointments on private channels without authorization. An attacker can obtain private channel identifiers through an information disclosure vulnerability, then use those IDs to create appointments on restricted channels that should only be accessible to verified patients. This undermines the platform's privacy model and allows unsolicited appointments on channels intended for confidential use.

Technologies: OpenReception Appointment-Booking-Software. Vendors: OpenReception.

Quick answers

Is CVE-2026-48076 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-48076 being exploited in the wild.
How severe is CVE-2026-48076?
Medium severity, with a CVSS score of 6.5, published 6 August 2026.
Which products and versions are affected?
OpenReception Appointment-Booking-Software 1.0.1 and prior.
Is there a fix for CVE-2026-48076?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-48076 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-48076?
Check whether you run OpenReception Appointment-Booking-Software at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability stems from a missing authorization check in the new-client booking flow. The bootstrap token issued by `bootstrap-verify` does not bind to `channelId`, and the `createNewClientWithAppointment` service function only validates `channel.archived = false` but omits the `channel.isPublic` check that exists in other appointment creation paths. An unauthenticated attacker can complete the bootstrap flow (16-bit proof-of-work with no rate limiting), obtain a valid booking token, and then submit a `create-new-client` request with an arbitrary `channelId` pointing to a private channel. Combined with V-10 (information disclosure of private channel IDs via unauthenticated schedule endpoint), this allows complete bypass of channel privacy restrictions. Appointments are created as `CONFIRMED` or `NEW` depending on the target channel's confirmation settings.

Affected products

  • OpenReception appointment booking software 1.0.1 and prior

Timeline

  • 2026-08-06: disclosed: Initial advisory published

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.