{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-37598 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-37598 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-37598 is a low-severity SQL injection vulnerability in n/a, published on 14 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-37598 and fix it if it is affected.\n\nWhat it is: CVE-2026-37598 is a low-severity SQL injection vulnerability in n/a, published on 14 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-37598 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-2026-37598/ (Markdown: https://insights.sbomify.com/CVE-2026-37598/index.md)","id":"CVE-2026-37598","markdown":"https://insights.sbomify.com/CVE-2026-37598/index.md","name":"CVE-2026-37598","record":{"aliases":["GHSA-h4hr-66wr-j77w"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Patient Appointment Scheduler","requires_auth":"high_privilege","summary":"Attackers can achieve remote code execution via SQL injection in the Patient Appointment Scheduler System settings update endpoint.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SourceCodester Patient Appointment Scheduler System v1.0 is vulnerable to arbitrary code execution (RCE) via /scheduler/classes/SystemSettings.php?f=update_settings.","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-2026-37598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2026-37600"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2026-37597"},"products":["n/a"],"published":"2026-04-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":"partial"},"state":"PUBLISHED","updated":"2026-04-14","vendors":["n/a"]},"summary":"Attackers can achieve remote code execution via SQL injection in the Patient Appointment Scheduler System settings update endpoint.","url":"https://insights.sbomify.com/CVE-2026-37598/"}