{"id":5061,"date":"2026-09-04T18:46:58","date_gmt":"2026-09-04T10:46:58","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-48080"},"modified":"2026-09-04T18:46:58","modified_gmt":"2026-09-04T10:46:58","slug":"cve-2026-48080","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-48080","title":{"rendered":"CVE-2026-48080 [HIGH] &#8211; OpenReception&#8217;s appointment booking software provides an end-to-end encrypted appointment"},"content":{"rendered":"<p>OpenReception&#8217;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&#8217;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&#8217;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&#8217;s `pg_read_server_files`, `COPY &#8230; 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&#8217;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.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>OpenReception&#8217;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 <\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-5061","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/5061","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5061"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5061"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5061"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}