{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-20692 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-20692 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-20692 is a high-severity SQL injection vulnerability in n/a, published on 27 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-20692 and fix it if it is affected.\n\nWhat it is: CVE-2020-20692 is a high-severity SQL injection vulnerability in n/a, published on 27 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-20692 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-20692/ (Markdown: https://insights.sbomify.com/CVE-2020-20692/index.md)","id":"CVE-2020-20692","markdown":"https://insights.sbomify.com/CVE-2020-20692/index.md","name":"CVE-2020-20692","record":{"aliases":["GHSA-c7gp-j3ff-rvrf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"GilaCMS","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary SQL commands via the GET parameter in GilaCMS, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gila_cms","vendor":"gilacms"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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":"GilaCMS v1.11.4 was discovered to contain a SQL injection vulnerability via the $_GET parameter in /src/core/controllers/cm.php.","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-20692","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":"Cross-Site Request Forgery in GilaCMS","id":"CVE-2020-20693"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2020-20691"},"products":["n/a"],"published":"2021-09-27","related":[{"cvss_score":9.9,"headline":"File upload in n/a","id":"CVE-2019-17536","kev_date_added":null,"published":"2019-10-13"},{"cvss_score":9.3,"headline":"Cross-site scripting in n/a","id":"CVE-2019-17535","kev_date_added":null,"published":"2019-10-13"},{"cvss_score":9.1,"headline":"File upload in n/a","id":"CVE-2020-5514","kev_date_added":null,"published":"2020-01-06"},{"cvss_score":8.8,"headline":"GilaCMS Cross Site Request Forgery vulnerability","id":"CVE-2020-20726","kev_date_added":null,"published":"2023-06-20"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery in GilaCMS","id":"CVE-2020-20693","kev_date_added":null,"published":"2021-09-27"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-20804","kev_date_added":null,"published":"2020-05-21"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-11456","kev_date_added":null,"published":"2019-04-22"}],"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 execute arbitrary SQL commands via the GET parameter in GilaCMS, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2020-20692/"}