{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15598 exists.","fix":"No fix has been published for CVE-2025-15598 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-15598 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15598 exists.\n\nAffected product: Dataease SQLBot. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-15598/ (Markdown: https://insights.sbomify.com/CVE-2025-15598/index.md)","id":"CVE-2025-15598","markdown":"https://insights.sbomify.com/CVE-2025-15598/index.md","name":"CVE-2025-15598","record":{"aliases":["GHSA-4wx6-wj3q-mf77"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SQLBot web application","requires_auth":"none","summary":"Attackers can bypass authentication in Dataease SQLBot by exploiting improper JWT signature verification in the embedded feature.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"sqlbot","vendor":"fit2cloud"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Dataease SQLBot JWT Token auth.py validateEmbedded signature verification","id":"CVE-2025-15598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"DOMPurify XSS via Textarea Rawtext Bypass in SAFE_FOR_XML","id":"CVE-2025-15599"},"packages":[],"prev":{"headline":"Dataease SQLBot API Endpoint assistant.py access control","id":"CVE-2025-15597"},"products":["SQLBot"],"published":"2026-03-03","related":[{"cvss_score":9.4,"headline":"SQLBot prompt injection allows arbitrary SQL execution and remote code execution","id":"CVE-2026-33324","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.7,"headline":"SQLBot: SSRF to Arbitrary File Read (AFR) via Rogue MySQL","id":"CVE-2026-32949","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.6,"headline":"SQLBot: Unauthorized Access Vulnerability","id":"CVE-2026-42463","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":8.6,"headline":"SQLBot: RCE via SQL Injection in Excel Upload Endpoint","id":"CVE-2026-32950","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.6,"headline":"SQLBot: Remote Code Execution via Terminology Poisoning","id":"CVE-2026-32622","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":7.7,"headline":"SQLBot uploadExcel Endpoint has Unauthenticated Arbitrary File Upload vulnerability","id":"CVE-2025-69285","kev_date_added":null,"published":"2026-01-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-03","vendors":["Dataease"]},"summary":"Attackers can bypass authentication in Dataease SQLBot by exploiting improper JWT signature verification in the embedded feature.","url":"https://insights.sbomify.com/CVE-2025-15598/"}