{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-104143 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-104143 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-104143 is a high-severity SQL injection vulnerability in dataease, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-104143 and fix it if it is affected.\n\nWhat it is: CVE-2026-104143 is a high-severity SQL injection vulnerability in dataease, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-104143 in the wild and no public exploit code.\n\nAffected product: dataease. 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-2026-104143/ (Markdown: https://insights.sbomify.com/CVE-2026-104143/index.md)","id":"CVE-2026-104143","markdown":"https://insights.sbomify.com/CVE-2026-104143/index.md","name":"CVE-2026-104143","record":{"aliases":["GHSA-h32f-m89w-g35f"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"DataEase visualization tool","requires_auth":"low_privilege","summary":"Authenticated users can inject SQL via crafted date format fields in DataEase, compromising backend database confidentiality, integrity, and availability.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-289","name":"Authentication Bypass by Alternate Name"}],"description":"DataEase is an open source data visualization and analysis tool. Prior to 2.10.26, authenticated users can store a crafted custom dateFormat for a dataset field. DatasetTableFieldDTO.dateFormat is inserted without validation into date conversion templates used by Dimension2SQLObj, CustomWhere2Str, Field2SQLObj, WhereTree2Str, and ExtWhere2Str. When a chart renders the field on a cross-datasource dataset, Calcite parsing is bypassed and the crafted format can directly alter the generated SQL. On a single-datasource dataset, exploitation additionally requires the payload to survive Calcite reserialization as a valid string literal. Successful exploitation can compromise the confidentiality, integrity, and availability of the backend database. This issue is fixed in version 2.10.26.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"DataEase: Stored SQL Injection via dateFormat field templates","id":"CVE-2026-104143","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"AdonisJS HTTP Server: Uncontrolled Resource Consumption and Inefficient Regular Expression Complexity","id":"CVE-2026-104150"},"packages":[],"prev":{"headline":"DataEase: Stored SQL Injection in group-field binning bounds","id":"CVE-2026-104142"},"products":["dataease"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["dataease"]},"summary":"Authenticated users can inject SQL via crafted date format fields in DataEase, compromising backend database confidentiality, integrity, and availability.","url":"https://insights.sbomify.com/CVE-2026-104143/"}