CVE-2026-42463: CWE-639: Authorization Bypass Through User-Controlled Key in dataease SQLBot
SQLBot versions prior to 1.8.0 contain an authorization bypass vulnerability classified as CWE-639 (Authorization Bypass Through User-Controlled Key). This vulnerability affects the /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema endpoints, allowing an attacker with limited privileges to access and modify database schemas and data sources belonging to other tenants or workspaces. The issue is fixed in version 1.8.0. The CVSS 4.0 base score is 8.6, indicating a high severity vulnerability.
AI Analysis
Technical Summary
SQLBot, an intelligent Text-to-SQL system, has an Insecure Direct Object Reference (IDOR) vulnerability prior to version 1.8.0 in its API endpoints /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema. This vulnerability allows an attacker with limited privileges to bypass authorization controls and access or modify database schemas and data sources of other tenants or workspaces. The vulnerability is tracked as CVE-2026-42463 and is fixed in SQLBot version 1.8.0. The CVSS 4.0 score of 8.6 reflects network attack vector, low attack complexity, no user interaction, and high impact on confidentiality and integrity.
Potential Impact
An attacker with limited privileges can exploit this vulnerability to access and modify database schemas and data sources belonging to other tenants or workspaces, potentially leading to unauthorized data exposure or tampering. This compromises the confidentiality and integrity of data managed by SQLBot instances running vulnerable versions.
Mitigation Recommendations
Upgrade SQLBot to version 1.8.0 or later, where this authorization bypass vulnerability is fixed. Since the vendor advisory confirms the fix in version 1.8.0, applying this official update is the recommended remediation. No other mitigation or temporary workaround is indicated in the available data.
CVE-2026-42463: CWE-639: Authorization Bypass Through User-Controlled Key in dataease SQLBot
Description
SQLBot versions prior to 1.8.0 contain an authorization bypass vulnerability classified as CWE-639 (Authorization Bypass Through User-Controlled Key). This vulnerability affects the /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema endpoints, allowing an attacker with limited privileges to access and modify database schemas and data sources belonging to other tenants or workspaces. The issue is fixed in version 1.8.0. The CVSS 4.0 base score is 8.6, indicating a high severity vulnerability.
CVSS v4.0
Score 8.6high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
SQLBot, an intelligent Text-to-SQL system, has an Insecure Direct Object Reference (IDOR) vulnerability prior to version 1.8.0 in its API endpoints /api/v1/datasource/exportDsSchema and /api/v1/datasource/uploadDsSchema. This vulnerability allows an attacker with limited privileges to bypass authorization controls and access or modify database schemas and data sources of other tenants or workspaces. The vulnerability is tracked as CVE-2026-42463 and is fixed in SQLBot version 1.8.0. The CVSS 4.0 score of 8.6 reflects network attack vector, low attack complexity, no user interaction, and high impact on confidentiality and integrity.
Potential Impact
An attacker with limited privileges can exploit this vulnerability to access and modify database schemas and data sources belonging to other tenants or workspaces, potentially leading to unauthorized data exposure or tampering. This compromises the confidentiality and integrity of data managed by SQLBot instances running vulnerable versions.
Mitigation Recommendations
Upgrade SQLBot to version 1.8.0 or later, where this authorization bypass vulnerability is fixed. Since the vendor advisory confirms the fix in version 1.8.0, applying this official update is the recommended remediation. No other mitigation or temporary workaround is indicated in the available data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-27T13:55:58.694Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a04f25dcbff5d8610127f41
Added to database: 05/13/2026, 21:51:25 UTC
Last enriched: 05/21/2026, 12:20:55 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.