{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69285 exists.","fix":"No fix has been published for CVE-2025-69285 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69285 is a high-severity vulnerability in dataease SQLBot, published on 21 Jan 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-69285 and fix it if it is affected.\n\nWhat it is: CVE-2025-69285 is a high-severity vulnerability in dataease SQLBot, published on 21 Jan 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-69285 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-69285/ (Markdown: https://insights.sbomify.com/CVE-2025-69285/index.md)","id":"CVE-2025-69285","markdown":"https://insights.sbomify.com/CVE-2025-69285/index.md","name":"CVE-2025-69285","record":{"aliases":["GHSA-crfm-cch4-hjpv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SQLBot data query system","requires_auth":"none","summary":"Unauthenticated attackers can upload arbitrary files to inject data into the database, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sqlbot","vendor":"fit2cloud"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"SQLBot is an intelligent data query system based on a large language model and RAG. Versions prior to 1.5.0 contain a missing authentication vulnerability in the /api/v1/datasource/uploadExcel endpoint, allowing a remote unauthenticated attacker to upload arbitrary Excel/CSV files and inject data directly into the PostgreSQL database. The endpoint is explicitly added to the authentication whitelist, causing the TokenMiddleware to bypass all token validation. Uploaded files are parsed by pandas and inserted into the database via to_sql() with if_exists='replace' mode. The vulnerability has been fixed in v1.5.0. No known workarounds are available.","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":"SQLBot uploadExcel Endpoint has Unauthenticated Arbitrary File Upload vulnerability","id":"CVE-2025-69285","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"RAGFlow has Predictable Token Generation Leading to Authentication Bypass Vulnerability","id":"CVE-2025-69286"},"packages":[],"prev":{"headline":"In plane.io, a Guest User to a Workspace can still be able to see list of members","id":"CVE-2025-69284"},"products":["SQLBot"],"published":"2026-01-21","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":6.3,"headline":"Dataease SQLBot JWT Token auth.py validateEmbedded signature verification","id":"CVE-2025-15598","kev_date_added":null,"published":"2026-03-03"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-21","vendors":["dataease"]},"summary":"Unauthenticated attackers can upload arbitrary files to inject data into the database, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2025-69285/"}