CVE-2026-48082: open-reception appointment-booking-software · Unthrottled Resource Allocation
Affects open-reception appointment-booking-softwareSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 1.0.6 when convenient.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade appointment-booking-software and open-reception/appointment-booking-software to 1.0.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| open-receptionappointment-booking-software | Affected
| Fixed in
|
GitHubopen-reception/appointment-booking-softwarepkg:github/open-reception/appointment-booking-softwareOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to OpenReception appointment-booking-software version 1.0.6 or later, which fixes the ineffective rate-limiting and throttle bypass issues. No other mitigation is indicated or necessary once patched.
Description
OpenReception's appointment booking software prior to version 1.0.6 has a weakness in its rate-limiting mechanism for unauthenticated clients. The proof-of-work challenge used as a rate limiter is set to a difficulty level that modern hardware can solve very quickly, making it ineffective against automated abuse. Additionally, the throttle mechanism can be bypassed by attackers supplying attacker-controlled values, allowing them to evade per-binding throttling. Version 1.0.6 addresses this issue.