{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20469 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20469 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20469 is a critical SQL injection vulnerability in n/a, published on 17 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20469 and fix it if it is affected.\n\nWhat it is: CVE-2018-20469 is a critical SQL injection vulnerability in n/a, published on 17 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-20469 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-20469/ (Markdown: https://insights.sbomify.com/CVE-2018-20469/index.md)","id":"CVE-2018-20469","markdown":"https://insights.sbomify.com/CVE-2018-20469/index.md","name":"CVE-2018-20469","record":{"aliases":["GHSA-gp44-m8rj-664r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sahi Pro web reports","requires_auth":"none","summary":"Attackers can inject SQL queries into the web reports module to execute system functions and access data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sahi_pro","vendor":"sahipro"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"An issue was discovered in Tyto Sahi Pro through 7.x.x and 8.0.0. A parameter in the web reports module is vulnerable to h2 SQL injection. This can be exploited to inject SQL queries and run standard h2 system functions.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-06-18","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-06-18","kind":"exploitdb","ref":"47006","stars":null,"title":"Sahi pro 8.x - SQL Injection"}],"tier":"poc_unverified"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2018-20469","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":"Path traversal in n/a","id":"CVE-2018-20470"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2018-20468"},"products":["n/a"],"published":"2019-06-17","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2019-15102","kev_date_added":null,"published":"2019-09-06"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-13597","kev_date_added":null,"published":"2019-07-14"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2018-20468","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2019-13063","kev_date_added":null,"published":"2019-09-23"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2018-20470","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-13066","kev_date_added":null,"published":"2019-10-29"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can inject SQL queries into the web reports module to execute system functions and access data.","url":"https://insights.sbomify.com/CVE-2018-20469/"}