Quick answers
- Is CVE-2026-65825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65825 being exploited in the wild.
- How severe is CVE-2026-65825?
- High severity, with a CVSS score of 7.5, published 23 October 2026.
- Which products and versions are affected?
- OpenReception Appointment-Booking-Software 2.1.0 and prior.
- Is there a fix for CVE-2026-65825?
- 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-65825 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-65825?
- 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 challenge_throttle table uses emailHash (tenant-independent) as its primary key but stores tenant_id as an unkeyed column. The recordFailedAttempt function writes failures with the caller's tenant ID but on conflict only updates attempt counts, leaving the row's tenant_id unchanged. checkThrottle reads throttle state scoped to the caller's tenant, so once tenant A owns a throttle record for an identifier, tenant B's checks never match, bypassing throttle enforcement. Combined with a weak six-digit PIN space (10^6) and a spoofable generic rate limiter, this enables online brute-force exhaustion in hours to days.
Affected products
- OpenReception appointment-booking-software 2.1.0 and prior
Timeline
- 2026-07-03: disclosed
- 2026-10-23: advisory