PatchSiren cyber security CVE debrief
CVE-2026-48080 open-reception CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-06T22:17:10.703Z and has not been modified since then. 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. Operators of OpenReception's appointment booking software should update to version 1.0.
- Vendor
- open-reception
- Product
- appointment-booking-software
- CVSS
- HIGH 8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-06
- Original CVE updated
- 2026-08-07
- Advisory published
- 2026-08-06
- Advisory updated
- 2026-08-07
Who should care
Operators of OpenReception's appointment booking software, particularly those who have configured a non-superuser PostgreSQL user, should be aware of this vulnerability and take steps to mitigate it. Additionally, security teams and vulnerability management teams should review the affected scope and severity of the vulnerability and plan for vendor-supported updates or mitigations through normal change control where exposure is confirmed.
Technical summary
The `GET /api/tenants/{id}` endpoint in OpenReception's appointment booking software returns the full tenant record, including the `databaseUrl` field, which contains the live PostgreSQL connection string. This string includes the user `postgres` with `rolsuper=true` and the plaintext password from `secrets/postgres_password.txt`. An attacker with access to this endpoint can use the credentials to read and modify data in any tenant database, as well as escalate privileges inside the database container. 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.
Defensive priority
Operators should prioritize updating to version 1.0.2 of OpenReception's appointment booking software to prevent unauthorized access to sensitive database credentials.
Recommended defensive actions
- Update to version 1.0.2 of OpenReception's appointment booking software
- Restrict access to the `GET /api/tenants/{id}` endpoint
- Monitor for suspicious activity on the PostgreSQL database
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE description provides details on the vulnerability, including the affected endpoint, the sensitive information disclosed, and the potential impact. However, the source corpus lacks information on the number of affected users or systems. To further assess the vulnerability, defenders should verify the deployment configurations of OpenReception's appointment booking software, review PostgreSQL database security settings, and monitor for suspicious activity. Additionally, defenders should consider the potential impact on tenant database isolation and the risks associated with the disclosure of the connection string.
Official resources
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-06T22:17:10.703Z and has not been modified since then.