SQLBot CVE-2026-121453

Exploitation requires an authenticated workspace administrator account (CVSS PR:H) with access to the /datasource/importToDb endpoint; it is not reachable by anonymous or low-privilege users. The attacker must supply a crafted filePath (absolute path or ../ sequences) that the server joins onto the upload directory without containment validation. A practical limit on impact is that the targeted file must be parseable as CSV or a spreadsheet to be imported into the excel_* tables and read back, so arbitrary binary or non-tabular files are not straightforwardly disclosed. The fix in commit 3d15c67 enforces that the resolved path stays within the upload base directory, so updating to the patched build removes the condition; the vendor patch is the stated remediation.

This is a moderate-severity, high-privilege information-disclosure flaw rather than a top-tier emergency. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N/VC:L) scores 5.1 and is internally consistent with the description: network-reachable, low complexity, but requiring PR:H - the attacker must already hold a workspace administrator account, which is the single largest limiting factor. There is no EPSS score, no CISA KEV listing, and no SSVC decision in the supplied data; the only priority signal is vuln.today's 'this_month' label, which aligns with 'patch in normal cycle' rather than act_now/emergency. A patch commit is confirmed and the issue was reported by a credible source (VulnCheck). The GitHub issue reference (#1434) documents the flaw but is not confirmed as working exploit code, so active or widespread exploitation should not be assumed. Net: a real but bounded issue - the PR:H requirement and the CSV/spreadsheet parsing constraint (only files that parse as a spreadsheet become readable) keep real-world risk below what a raw 'path traversal / arbitrary file read' label might suggest. No key signals conflict; the main gap is the absence of EPSS/KEV/SSVC to gauge exploitation likelihood.

A malicious or compromised workspace administrator calls the /datasource/importToDb endpoint and supplies a filePath containing ../ sequences or an absolute path instead of a legitimate upload name. The server joins this directly onto the upload directory (os.path.join(path, import_req.filePath)) with no containment check, so the attacker imports another workspace's upload or a server-side file that parses as CSV/spreadsheet into a queryable excel_* table and then reads it back. A public GitHub issue (#1434) describes the vulnerability, but no verified working exploit code is identified in the provided data.