{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-21060 exists.","fix":"No fix has been published for CVE-2020-21060 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-21060 is a high-severity SQL injection vulnerability in n/a, published on 4 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-21060 and fix it if it is affected.\n\nWhat it is: CVE-2020-21060 is a high-severity SQL injection vulnerability in n/a, published on 4 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-21060 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-21060/ (Markdown: https://insights.sbomify.com/CVE-2020-21060/index.md)","id":"CVE-2020-21060","markdown":"https://insights.sbomify.com/CVE-2020-21060/index.md","name":"CVE-2020-21060","record":{"aliases":["GHSA-h35h-4f93-342q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PHPMyWind CMS","requires_auth":"low_privilege","summary":"Remote attackers can exploit SQL injection in the admin delete function to gain privileges and access or modify data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phpmywind","vendor":"phpmywind"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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 found in PHPMyWind v.5.6 allows a remote attacker to gain privileges via the delete function of the administrator management page.","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-21060","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":"Memory corruption in n/a","id":"CVE-2020-21066"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-21058"},"products":["n/a"],"published":"2023-04-04","related":[{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2020-21400","kev_date_added":null,"published":"2023-06-20"},{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2021-39503","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":7.2,"headline":"Command injection in n/a","id":"CVE-2020-18885","kev_date_added":null,"published":"2021-08-20"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2020-18886","kev_date_added":null,"published":"2021-08-20"},{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2018-17131","kev_date_added":null,"published":"2018-09-17"},{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2018-17132","kev_date_added":null,"published":"2018-09-17"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["n/a"]},"summary":"Remote attackers can exploit SQL injection in the admin delete function to gain privileges and access or modify data.","url":"https://insights.sbomify.com/CVE-2020-21060/"}