# CVE-2026-48074: OpenReception: Staff deletion removes pending invites cross-tenant by email match

> A tenant admin can delete pending invites in other tenants by deleting a staff member with a matching email address.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-6f8g-wfxp-mqxw

## What is CVE-2026-48074?

CVE-2026-48074 is a low-severity missing authorization vulnerability in open-reception appointment-booking-software, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.6, when a TENANT_ADMIN deletes an existing staff user, the underlying `StaffService.deleteStaffMember()` runs an additional invite cleanup that deletes from the central `user_invite` table by email. The `email` clause has no `tenantId` predicate. Any pending invite in any tenant that shares the deleted staff's email is removed. A TENANT_ADMIN of tenant A who deletes a staff record with email `victim[@]example[.]com` also deletes the pending invite for `victim[@]example[.]com` in tenant B, even though they have no relationship to tenant B. The user-side delete is correctly scoped (`eq(user.id, staffId), eq(user.tenantId, tenantId)`), and the pending-invite-only delete path (when `staffId` is itself an invite ID) is also tenant-scoped. The bug is specifically in the invite cleanup that runs as a side effect of deleting an existing staff user. Version 1.0.6 patches the issue.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-48074?


## How do I fix CVE-2026-48074?

No fix has been published for CVE-2026-48074 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48074 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48074 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48074 and fix it if it is affected.

What it is: CVE-2026-48074 is a low-severity missing authorization vulnerability in open-reception appointment-booking-software, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48074 exists.

Affected product: open-reception appointment-booking-software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48074/ (Markdown: https://insights.sbomify.com/CVE-2026-48074/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48074
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48074
- OSV: https://osv.dev/vulnerability/CVE-2026-48074

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48074/
Summaries are generated and may contain mistakes; the official description above is the record.