{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-39375 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-39375 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-39375 is a high-severity SQL injection vulnerability in n/a, published on 24 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-39375 and fix it if it is affected.\n\nWhat it is: CVE-2021-39375 is a high-severity SQL injection vulnerability in n/a, published on 24 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-39375 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2021-39375/ (Markdown: https://insights.sbomify.com/CVE-2021-39375/index.md)","id":"CVE-2021-39375","markdown":"https://insights.sbomify.com/CVE-2021-39375/index.md","name":"CVE-2021-39375","record":{"aliases":["GHSA-3937-gxfq-r6h8"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Healthcare EMR","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary SQL commands via the FilterValue parameter in Philips Tasy EMR, potentially accessing or modifying patient data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tasy_electronic_medical_record","vendor":"philips"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Philips Healthcare Tasy Electronic Medical Record (EMR) 3.06 allows SQL injection via the WAdvancedFilter/getDimensionItemsByCode FilterValue parameter.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2021-39375","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2021-39376"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2021-39373"},"products":["n/a"],"published":"2021-08-24","related":[{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2021-39376","kev_date_added":null,"published":"2021-08-24"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary SQL commands via the FilterValue parameter in Philips Tasy EMR, potentially accessing or modifying patient data.","url":"https://insights.sbomify.com/CVE-2021-39375/"}