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.
CVE-2026-63307
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-17. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 14.0%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 17, 2026ForgeCode Arbitrary Code Execution via Unvetted .mcp.json in Untrusted Repository | Advisories | VulnCheck
https://www.vulncheck.com/advisories/forgecode-arbitrary-code-execution-via-unvetted-mcp-json-in-untrusted-repositoryChat2DB Community 5.3.0
Patch available: OtterMind/Chat2DB v5.3.0
https://github.com/OtterMind/Chat2DB/releases/tag/v5.3.0Bug: Datasource credential IDOR - any user reads any user's database password · Issue #1839 · OtterMind/Chat2DB · GitHub
https://github.com/OtterMind/Chat2DB/issues/1839Vendor Advisories for CVE-2026-63307(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-17 18:31 UTCEG score recompute
- 2026-07-17 18:31 UTCGHSA enrichment
- 2026-07-17 18:03 UTCEG score recompute
- 2026-07-17 16:20 UTCEG score recompute
- 2026-07-17 16:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-63307?
When was CVE-2026-63307 disclosed?
Is CVE-2026-63307 actively exploited?
What is the CVSS score of CVE-2026-63307?
How do I remediate CVE-2026-63307?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63307
Is Your Infrastructure Affected by CVE-2026-63307?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.