EUVD-2026-45212
GHSA-6h56-q7r6-j7xg
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network API reachable by any authenticated low-privilege user (PR:L, AV:N, AC:L, UI:N) with high confidentiality impact from leaked credentials and no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
Chat2DB before 5.3.0 contains an insecure direct object reference vulnerability in the GET /api/connection/datasource/{id} endpoint. The handler calls dataSourceService.queryExistent(id, ...) without an ownership check and returns the decrypted password field, allowing any authenticated non-admin user to enumerate datasource IDs and read the plaintext database credentials of datasources owned by other users.
AnalysisAI
Insecure direct object reference in Chat2DB before 5.3.0 lets any authenticated non-admin user read the decrypted database credentials of datasources belonging to other users by enumerating IDs against GET /api/connection/datasource/{id}. Because the handler returns the plaintext password field and omits an ownership check, a single low-privileged account can harvest every other tenant's stored connection secrets. No public exploit has been identified at time of analysis, but exploitation is trivial and the EPSS/KEV signals were not supplied in the input.
Technical ContextAI
Chat2DB is an AI-assisted database client and management tool (vendor 'ottermind', CPE cpe:2.3:a:ottermind:chat2db) that stores connection profiles ('datasources') including encrypted credentials for backend databases. The flaw is CWE-639 (Authorization Bypass Through User-Controlled Key): the REST endpoint GET /api/connection/datasource/{id} passes the caller-supplied {id} straight into dataSourceService.queryExistent(id, ...) with no check that the requesting user owns the record, and the response serializes the decrypted password field. Because datasource IDs are enumerable and the server itself decrypts the secret before returning it, at-rest encryption provides no protection against an authenticated API caller.
RemediationAI
Vendor-released patch: upgrade to Chat2DB 5.3.0 or later (release https://github.com/OtterMind/Chat2DB/releases/tag/v5.3.0, or Docker image chat2db/chat2db:5.3.0); note that 5.3.0 is not an in-place upgrade from 0.3.x, so back up and migrate data before installing. If immediate patching is not possible in a multi-user deployment, restrict network access to the /api/connection/datasource/ endpoints to trusted administrators (for example via a reverse-proxy allow-list), limit accounts to a single trusted user since the local-first design assumes no multi-tenancy, and rotate any database credentials that were stored in shared instances because they may already have been readable by other users - the trade-off of the proxy restriction is that legitimate low-privilege users lose datasource read access via the API until the upgrade is applied.
An unrestricted file upload vulnerability exists in CodePhiliaX Chat2DB versions up to 0.3.7 in the JDBC Driver Upload f
CodePhiliaX Chat2DB versions up to 0.3.7 contain a SQL injection vulnerability in the Database Export Handler component
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today