# CVE-2026-48080: Information disclosure in appointment-booking-software

> Authenticated tenant admins can retrieve live PostgreSQL superuser credentials, enabling cross-tenant data access and potential database container compromise.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **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-v7fw-6xpm-7gj9

## What is CVE-2026-48080?

CVE-2026-48080 is a high-severity 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.2, the `GET /api/tenants/{id}` endpoint returns the full tenant record to any authenticated `TENANT_ADMIN` of that tenant, including the `databaseUrl` field. This field contains the live PostgreSQL connection string the application uses to connect to that tenant's database. In the tested official `docker-compose.prod.yml` deployment, the connection string contained the user `postgres` with `rolsuper=true` and the plaintext password from `secrets/postgres_password.txt`. Operators who configure a non-superuser PostgreSQL user via `secrets/postgres_user.txt` would expose a less privileged credential, but the disclosure of the connection string itself is independent of that choice. The same credential applies to every database managed by that PostgreSQL instance: the central `appointment_booking` database, every per-tenant database (one per tenant), and the postgres administrative database. A `TENANT_ADMIN` of one tenant who can reach `postgres:5432` (directly via internal network, indirectly via any SSRF, RCE, or file-read in the application) can read every other tenant's appointment ciphertexts, key shares, and metadata; read the central user table, including all `GLOBAL_ADMIN` accounts, password hashes, and session records; modify or delete any data in any tenant database; and/or i a superuser-scoped deployment: use PostgreSQL's `pg_read_server_files`, `COPY ... FROM PROGRAM`, and `CREATE EXTENSION` for further escalation inside the database container. This breaks the per-tenant database isolation that is otherwise the primary cross-tenant control in the application. The application code carefully scopes most queries to the calling tenant's database, but those scopings are irrelevant once the attacker holds the credentials that bypass the application entirely. Version 1.0.2 fixes the issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-48080 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48080 is a high-severity 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-48080 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-48080/ (Markdown: https://insights.sbomify.com/CVE-2026-48080/index.md)
```

## Sources

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

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