Skip to main content
VulnerabilityPublished

CVE-2025-15597: Dataease SQLBot · Improper Access Controls

Affects Dataease SQLBotSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
DataeaseSQLBotAffected
  • 1.0 – 1.4.0
5 affected builds
Fixed in–
GitHubdataease/SQLBotpkg:github/dataease/SQLBotOther threatsAffected
  • 1.0 – 1.4.0
5 affected builds
Fixed in–

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

AI-suggested

  1. Immediately upgrade Dataease SQLBot to version 1.5.0 or later, which contains the official patch (commit d640ac31d1ce64ce90e06cf7081163915c9fc28c) addressing the improper access control issue.
  2. Until patching is complete, restrict network access to the affected API endpoints by implementing firewall rules or network segmentation to limit exposure to trusted hosts only.
  3. Conduct a thorough audit of API access logs to detect any unusual or unauthorized access attempts targeting the assistant.py endpoints.
  4. Implement additional application-layer access controls or API gateways that enforce strict authentication and authorization policies as a compensating control.
  5. Review and harden the configuration of SQLBot deployments to minimize unnecessary API exposure and disable unused endpoints.
  6. Educate security and DevOps teams about the vulnerability and ensure rapid response plans are in place for any suspicious activity.
  7. Monitor threat intelligence feeds for any emerging exploit code or attack campaigns targeting this vulnerability to enable timely defensive actions.

Description

A vulnerability has been found in Dataease SQLBot up to 1.4.0. This affects an unknown function of the file backend/apps/system/api/assistant.py of the component API Endpoint. Such manipulation leads to improper access controls. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.5.0 mitigates this issue. The name of the patch is d640ac31d1ce64ce90e06cf7081163915c9fc28c. Upgrading the affected component is recommended. Multiple endpoints are affected. The vendor was contacted early about this disclosure.

References

Community reviews

Loading reviews…