Vulnerability in OpenReception (CVE-2026-48088)
Summary
Vulnerability in OpenReception (CVE-2026-48088). Confidential information can be exposed externally. Exploitable via POST /api/tenants/{tenantId}/staff/{staffId}/crypto.
Original description
The description as published by the source.
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.4, the route POST /api/tenants/{tenantId}/staff/{staffId}/crypto accepts and stores attacker-controlled ML-KEM-768 public keys against any tenant on the platform without authentication. The handler logs an "Unauthorized crypto key storage attempt" warning when neither a session nor a registration cookie is present, then proceeds to insert the row regardless. The platform's E2E claim that "even administrators cannot view sensitive information" is broken: any unauthenticated network attacker can register themselves as an additional encryption recipient for any tenant's future patient appointments. A second variant of the bug suppresses the unauthorized-warning log entry. The Zod schema makes the email field optional. When the request body omits email and the request carries no registration cookie, the comparison registrationEmail === email becomes undefined === undefined, which evaluates to true. The handler treats the request as a legitimate registration flow, skips the warning entirely, and stores the row. Successful storage is still recorded as an [info] log line, but the security-relevant warning that operators are most likely to monitor or alert on is gone. The staff_crypto table has no unique constraint on user_id, so an arbitrary number of attacker rows can coexist for the same staff identifier and all return as `is_active=tru…
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48088 has been found in OpenReception.
Attackers can target a specific entry point like POST /api/tenants/{tenantId}/staff/{staffId}/crypto over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OpenReception CVE-2026-48088" on the vendor's site.
CVE-2026-48088 (OpenReception) — CWE-862 / CVSS v3 9.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/tenants/{tenantId}/staff/{staffId}/crypto / GET /api/tenants/{id}/appointments/staff-public-keys / email / true
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in OpenReception. Attackers reach the vulnerable code path via POST /api/tenants/{tenantId}/staff/{staffId}/crypto without authentication.
Check the vendor advisory for the affected versions of OpenReception. Attack surface: POST /api/tenants/{tenantId}/staff/{staffId}/crypto / GET /api/tenants/{id}/appointments/staff-public-keys / email / true.
Severity: Critical (CVSS 9.4/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/tenants/{tenantId}/staff/{staffId}/crypto requests with malformed payloads or SQL meta-characters. Run grep -r 'OpenReception' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'OpenReception' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OpenReceptionを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/tenants/{tenantId}/staff/{staffId}/crypto' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/tenants/{tenantId}/staff/{staffId}/cryptoへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/tenants/{tenantId}/staff/{staffId}/crypto on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。