{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-20361 exists.","fix":"No fix has been published for CVE-2019-20361 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20361 is a high-severity SQL injection vulnerability in n/a, published on 8 Jan 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-2019-20361 and fix it if it is affected.\n\nWhat it is: CVE-2019-20361 is a high-severity SQL injection vulnerability in n/a, published on 8 Jan 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-2019-20361 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-2019-20361/ (Markdown: https://insights.sbomify.com/CVE-2019-20361/index.md)","id":"CVE-2019-20361","markdown":"https://insights.sbomify.com/CVE-2019-20361/index.md","name":"CVE-2019-20361","record":{"aliases":["GHSA-3m22-3wj5-cpwf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"A blind SQL injection vulnerability in the Email Subscribers \u0026 Newsletters plugin allows attackers to read database contents via the hash parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"email_subscribers_\\\u0026_newsletters","vendor":"icegram"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AC:L/AV:N/A:L/C:L/I:L/PR:N/S:C/UI:N","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"There was a flaw in the WordPress plugin, Email Subscribers \u0026 Newsletters before 4.3.1, that allowed SQL statements to be passed to the database in the hash parameter (a blind SQL injection vulnerability).","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-11-13","github_poc":1,"max_poc_stars":0,"metasploit":1,"nuclei":0,"refs":[{"date":"2019-11-13","kind":"metasploit","ref":"auxiliary/scanner/http/wp_email_sub_news_sqli","stars":null,"title":"WordPress Email Subscribers and Newsletter Hash SQLi Scanner"},{"date":"2020-07-26","kind":"exploitdb","ref":"48699","stars":null,"title":"WordPress Plugin Email Subscribers \u0026 Newsletters 4.2.2 - 'hash' SQL Injection (Unauthenticated)"},{"date":"2021-03-18T00:22:05Z","kind":"github_poc","ref":"https://github.com/jerrylewis9/CVE-2019-20361-EXPLOIT","stars":0,"title":"There was a flaw in the WordPress plugin, Email Subscribers \u0026 Newsletters before 4.3.1, that allowed SQL statements to be passed to the database in the hash parameter (a blind SQL injection vulnerability)."}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2019-20361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-20362"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2019-20360"},"products":["n/a"],"published":"2020-01-08","related":[{"cvss_score":9.8,"headline":"SQL injection in Email Subscribers \u0026 Newsletters – Email Marketing, Post Notifications \u0026 Newsletter Plugin for WordPress","id":"CVE-2024-6172","kev_date_added":null,"published":"2024-07-02"},{"cvss_score":9.8,"headline":"Email Subscribers by Icegram Express \u003c= 5.7.20 - Unauthenticated SQL Injection via hash","id":"CVE-2024-4295","kev_date_added":null,"published":"2024-06-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-13569","kev_date_added":null,"published":"2019-07-19"},{"cvss_score":8.8,"headline":"Icegram Express \u003c 5.5.1 - Subscriber+ SQLi","id":"CVE-2022-3981","kev_date_added":null,"published":"2022-12-12"},{"cvss_score":8.8,"headline":"Email Subscribers \u0026 Newsletters \u003c 5.3.2 - Subscriber+ Blind SQL injection","id":"CVE-2022-0439","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2018-6015","kev_date_added":null,"published":"2018-01-26"}],"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":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A blind SQL injection vulnerability in the Email Subscribers \u0026 Newsletters plugin allows attackers to read database contents via the hash parameter.","url":"https://insights.sbomify.com/CVE-2019-20361/"}