{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-20340 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-20340 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-20340 is a high-severity SQL injection vulnerability in n/a, published on 1 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-20340 and fix it if it is affected.\n\nWhat it is: CVE-2020-20340 is a high-severity SQL injection vulnerability in n/a, published on 1 Sep 2021. 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-2020-20340 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-2020-20340/ (Markdown: https://insights.sbomify.com/CVE-2020-20340/index.md)","id":"CVE-2020-20340","markdown":"https://insights.sbomify.com/CVE-2020-20340/index.md","name":"CVE-2020-20340","record":{"aliases":["GHSA-c52c-58rq-pmph"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"S-CMS","requires_auth":"none","summary":"Attackers can exploit SQL injection in S-CMS to access sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"s-cms","vendor":"s-cms"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL injection vulnerability in the 4.edu.php\\conn\\function.php component of S-CMS v1.0 allows attackers to access sensitive database information.","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-2020-20340","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2020-20341"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2020-20335"},"products":["n/a"],"published":"2021-09-01","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-51048","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-51049","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-51050","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-51051","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-51052","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-23336","kev_date_added":null,"published":"2022-02-14"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-10708","kev_date_added":null,"published":"2019-04-02"}],"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 exploit SQL injection in S-CMS to access sensitive database information.","url":"https://insights.sbomify.com/CVE-2020-20340/"}