# CVE-2025-15598: Dataease SQLBot JWT Token auth.py validateEmbedded signature verification

> Attackers can bypass authentication in Dataease SQLBot by exploiting improper JWT signature verification in the embedded feature.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-4wx6-wj3q-mf77

## What is CVE-2025-15598?

CVE-2025-15598 is a medium-severity authentication bypass vulnerability in Dataease SQLBot, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Dataease SQLBot up to 1.5.1. This impacts the function validateEmbedded of the file backend/apps/system/middleware/auth.py of the component JWT Token Handler. Performing a manipulation results in improper verification of cryptographic signature. The attack can be initiated remotely. The attack is considered to have high complexity. The exploitability is said to be difficult. The exploit has been made public and could be used. A comment in the source code warns users about using this feature. The vendor was contacted early about this disclosure.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2025-15598?

It affects 1 product.


Products: Fit2cloud Sqlbot.

## How do I fix CVE-2025-15598?

No fix has been published for CVE-2025-15598 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15598 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15598 exists.

## Other vulnerabilities in Dataease SQLBot

- [CVE-2026-33324](https://insights.sbomify.com/CVE-2026-33324/): SQLBot prompt injection allows arbitrary SQL execution and remote code execution (critical 9.4)
- [CVE-2026-32949](https://insights.sbomify.com/CVE-2026-32949/): SQLBot: SSRF to Arbitrary File Read (AFR) via Rogue MySQL (high 8.7)
- [CVE-2026-42463](https://insights.sbomify.com/CVE-2026-42463/): SQLBot: Unauthorized Access Vulnerability (high 8.6)
- [CVE-2026-32950](https://insights.sbomify.com/CVE-2026-32950/): SQLBot: RCE via SQL Injection in Excel Upload Endpoint (high 8.6)
- [CVE-2026-32622](https://insights.sbomify.com/CVE-2026-32622/): SQLBot: Remote Code Execution via Terminology Poisoning (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15598 and fix it if it is affected.

What it is: CVE-2025-15598 is a medium-severity authentication bypass vulnerability in Dataease SQLBot, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15598 exists.

Affected product: Dataease SQLBot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15598/ (Markdown: https://insights.sbomify.com/CVE-2025-15598/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15598
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15598
- OSV: https://osv.dev/vulnerability/CVE-2025-15598

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15598/
Summaries are generated and may contain mistakes; the official description above is the record.