{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-23966 exists.","fix":"No fix has been published for CVE-2020-23966 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-23966 is a critical SQL injection vulnerability in n/a, published on 8 May 2023. 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-23966 and fix it if it is affected.\n\nWhat it is: CVE-2020-23966 is a critical SQL injection vulnerability in n/a, published on 8 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-23966 exists.\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-23966/ (Markdown: https://insights.sbomify.com/CVE-2020-23966/index.md)","id":"CVE-2020-23966","markdown":"https://insights.sbomify.com/CVE-2020-23966/index.md","name":"CVE-2020-23966","record":{"aliases":["GHSA-mm96-9vx8-pfhj"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Victor CMS","requires_auth":"none","summary":"Attackers can execute arbitrary commands via SQL injection in Victor CMS through the post parameter in a crafted GET request.","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":9.8,"severity":"critical","source":"cisa-adp","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":"SQL Injection vulnerability in victor cms 1.0 allows attackers to execute arbitrary commands via the post parameter to /post.php in a crafted GET request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2020-23966","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-23967"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-23962"},"products":["n/a"],"published":"2023-05-08","related":[{"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-29","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via SQL injection in Victor CMS through the post parameter in a crafted GET request.","url":"https://insights.sbomify.com/CVE-2020-23966/"}