OpenReception: one tenant's throttle row disables the PIN brute-force throttle for the same identifier in other tenants
Impact
OpenReception's appointment booking software, versions 2.1.0 and prior, has a weakness where one tenant's throttle row can disable the PIN brute-force throttle for the same identifier in other tenants, potentially allowing access to a client's appointment data. The weakness is due to improper restriction of excessive authentication attempts. No patches are publicly available.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
open-reception · GitHub_M
appointment-booking-software
1 range
open-reception · GitHub_M
appointment-booking-software
Compare with this publisher’s ranges. This does not inspect your installation.
affected
<= 2.1.0
Other versions: unknown
Original source description
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. In versions 2.1.0 and prior, a returning client's six-digit booking PIN can be brute-forced online in the victim tenant. A successful guess yields the client's booking access token, granting access to that client's appointment tunnel, which holds their end-to-end-encrypted appointment data, and the ability to act as the client, for example adding or cancelling appointments in the tunnel. The bypass is cross-tenant: state owned by one tenant removes an authentication protection of a different tenant. This crossing of the tenant boundary is the basis for the scope-changed vector. At time of publication, there are no publicly available patches.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-65825View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.