{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-27615 exists.","fix":"No fix has been published for CVE-2020-27615 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27615 is a critical SQL injection vulnerability in n/a, published on 21 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-27615 and fix it if it is affected.\n\nWhat it is: CVE-2020-27615 is a critical SQL injection vulnerability in n/a, published on 21 Oct 2020. 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-27615 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-27615/ (Markdown: https://insights.sbomify.com/CVE-2020-27615/index.md)","id":"CVE-2020-27615","markdown":"https://insights.sbomify.com/CVE-2020-27615/index.md","name":"CVE-2020-27615","record":{"aliases":["GHSA-vf5c-prqq-g9f7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An SQL injection vulnerability in the Loginizer WordPress plugin allows attackers to execute arbitrary SQL commands and potentially cross-site scripting attacks.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"loginizer","vendor":"loginizer"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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":"The Loginizer plugin before 1.6.4 for WordPress allows SQL injection (with resultant XSS), related to loginizer_login_failed and lz_valid_ip.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-10-21","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":1,"refs":[{"date":"2020-10-21","kind":"metasploit","ref":"auxiliary/scanner/http/wp_loginizer_log_sqli","stars":null,"title":"WordPress Loginizer log SQLi Scanner"},{"date":null,"kind":"nuclei","ref":"http/cves/2020/CVE-2020-27615.yaml","stars":null,"title":"WordPress Loginizer \u003c 1.6.4 – Unauthenticated SQL Injection via `log` Parameter"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2020-27615","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-27616"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2020-27614"},"products":["n/a"],"published":"2020-10-21","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2017-12650","kev_date_added":null,"published":"2017-08-07"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-12651","kev_date_added":null,"published":"2017-08-07"},{"cvss_score":8.1,"headline":"Loginizer Security and Loginizer \u003c= 1.9.2 - Authentication Bypass via WordPress.com OAuth provider","id":"CVE-2024-10097","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":7.1,"headline":"WordPress Loginizer Plugin \u003c= 1.7.5 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2022-45084","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":6.1,"headline":"Loginizer 1.7.8 - Reflected XSS","id":"CVE-2023-2296","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-11366","kev_date_added":null,"published":"2018-05-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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An SQL injection vulnerability in the Loginizer WordPress plugin allows attackers to execute arbitrary SQL commands and potentially cross-site scripting attacks.","url":"https://insights.sbomify.com/CVE-2020-27615/"}