Skip to main content
VulnerabilityPublished

CVE-2026-130595: dataease SQLBot · Incomplete List of Disallowed Inputs

Affects dataease SQLBotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium.

Data as of 17 Nov 2026, 14:11 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.0
CNA (VulnCheck)CVSS 3.15.9
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
dataeaseSQLBotAffected
  • >=1.10.0 <=1.10.3
Fixed in–
GitHubSQLBotpkg:github/SQLBotOther threatsAffected
  • >=1.10.0 <=1.10.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict authenticated user privileges to minimize risk and monitor for updates from the vendor.

Description

SQLBot versions 1.10.0 through 1.10.3 contain a vulnerability where the denylist for dangerous PostgreSQL functions is incomplete. The denylist uses the string 'postgresql' while the actual function lookups use 'pg', allowing authenticated users to bypass the check and execute file read/write operations on the database host via functions like pg_read_file and pg_write_file.

References

Community reviews

Loading reviews…