The vulnerability in SQLBot results from a chained flaw that allows an authenticated user to upload a malicious Excel file containing untampered terminology. The terminology descriptions are stored without sanitization and are later injected into the large‑language‑model system prompt without semantic fencing. This chain permits an attacker to ask the model to produce dangerous PostgreSQL commands, such as COPY … TO PROGRAM, which are then executed under the database or application server with postgres user privileges. The net effect is full remote code execution on the database or application server.

Products impacted are dataease SQLBot version 1.5.0 and earlier. The CVE references a patch in v1.6.0, indicating that those earlier releases lack the necessary fixes. No other vendors or product versions are explicitly listed in the CNA data.

The CVSS score of 8.6 classifies the issue as high severity, while the EPSS score of less than 1% indicates that exploitation is considered unlikely at present. Because the vulnerability is not listed in the CISA KEV catalog, it is not a known exploited vulnerability. The attack vector is inferred to require an authenticated user who can upload Excel files, meaning that internal users or compromised accounts pose the primary risk. The chain of missing permission checks, unsanitized storage, and lack of semantic fencing suggests that the vulnerability can be exercised from a normal application flow without additional bypasses.