{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-23945 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-23945 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-23945 is a high-severity SQL injection vulnerability in n/a, published on 27 Oct 2020. 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-23945 and fix it if it is affected.\n\nWhat it is: CVE-2020-23945 is a high-severity SQL injection vulnerability in n/a, published on 27 Oct 2020. 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-23945 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-23945/ (Markdown: https://insights.sbomify.com/CVE-2020-23945/index.md)","id":"CVE-2020-23945","markdown":"https://insights.sbomify.com/CVE-2020-23945/index.md","name":"CVE-2020-23945","record":{"aliases":["GHSA-9q2m-8p9j-9x39"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Victor CMS","requires_auth":"none","summary":"Attackers can exploit SQL injection in Victor CMS to read sensitive database information via the cat_id parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"victor_cms","vendor":"victor_cms_project"}],"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 exists in Victor CMS V1.0 in the cat_id parameter of the category.php file. This parameter can be used by sqlmap to obtain data information in the database.","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-23945","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":"Cross-site scripting in n/a","id":"CVE-2020-23957"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-23938"},"products":["n/a"],"published":"2020-10-27","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-23966","kev_date_added":null,"published":"2023-05-08"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-26201","kev_date_added":null,"published":"2022-03-04"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-25203","kev_date_added":null,"published":"2021-07-23"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-29280","kev_date_added":null,"published":"2020-12-02"},{"cvss_score":8.8,"headline":"Victor CMS 1.0 - 'post' SQL Injection","id":"CVE-2020-37076","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2020-35597","kev_date_added":null,"published":"2022-06-16"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2022-27478","kev_date_added":null,"published":"2022-04-21"}],"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 Victor CMS to read sensitive database information via the cat_id parameter.","url":"https://insights.sbomify.com/CVE-2020-23945/"}