{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000650 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1000650 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1000650 is a high-severity SQL injection vulnerability in n/a, published on 20 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1000650 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000650 is a high-severity SQL injection vulnerability in n/a, published on 20 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1000650 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-2018-1000650/ (Markdown: https://insights.sbomify.com/CVE-2018-1000650/index.md)","id":"CVE-2018-1000650","markdown":"https://insights.sbomify.com/CVE-2018-1000650/index.md","name":"CVE-2018-1000650","record":{"aliases":["GHSA-4ggq-ghmc-h6h3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LibreHealth EHR","requires_auth":"low_privilege","summary":"Attackers can execute malicious database queries via user-controlled parameters in LibreHealth EHR, potentially reading or modifying sensitive data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"librehealth_ehr","vendor":"librehealth"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"LibreHealthIO lh-ehr version REL-2.0.0 contains a SQL Injection vulnerability in Show Groups Popup SQL query functions that can result in Ability to perform malicious database queries. This attack appear to be exploitable via User controlled parameters.","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":"SQL injection in n/a","id":"CVE-2018-1000650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2018-1000651"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2018-1000649"},"products":["n/a"],"published":"2018-08-20","related":[{"cvss_score":9,"headline":"Cross-site scripting in n/a","id":"CVE-2020-11436","kev_date_added":null,"published":"2020-07-15"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2022-31496","kev_date_added":null,"published":"2022-06-08"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2022-29938","kev_date_added":null,"published":"2022-05-05"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-23829","kev_date_added":null,"published":"2020-09-01"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-11438","kev_date_added":null,"published":"2020-07-15"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2020-11439","kev_date_added":null,"published":"2020-07-15"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2018-1000839","kev_date_added":null,"published":"2018-12-20"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can execute malicious database queries via user-controlled parameters in LibreHealth EHR, potentially reading or modifying sensitive data.","url":"https://insights.sbomify.com/CVE-2018-1000650/"}