{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8596 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8596 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8596 is a high-severity SQL injection vulnerability in n/a, published on 10 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-8596 and fix it if it is affected.\n\nWhat it is: CVE-2020-8596 is a high-severity SQL injection vulnerability in n/a, published on 10 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-8596 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-8596/ (Markdown: https://insights.sbomify.com/CVE-2020-8596/index.md)","id":"CVE-2020-8596","markdown":"https://insights.sbomify.com/CVE-2020-8596/index.md","name":"CVE-2020-8596","record":{"aliases":["GHSA-xw39-q6xj-4gq5"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers can exploit SQL injection in the Participants Database plugin to exfiltrate data and potentially execute code.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"participants_database","vendor":"xnau"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/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":"participants-database.php in the Participants Database plugin 1.9.5.5 and previous versions for WordPress has a time-based SQL injection vulnerability via the ascdesc, list_filter_count, or sortBy parameters. It is possible to exfiltrate data and potentially execute code (if certain conditions are met).","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-8596","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":"Memory corruption in n/a","id":"CVE-2020-8597"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-8595"},"products":["n/a"],"published":"2020-02-10","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2014-3961","kev_date_added":null,"published":"2014-06-04"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-14126","kev_date_added":null,"published":"2017-09-04"},{"cvss_score":5.4,"headline":"WordPress Participants Database Plugin \u003c= 2.4.9 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-31235","kev_date_added":null,"published":"2023-11-09"},{"cvss_score":4.3,"headline":"WordPress Participants Database Plugin \u003c= 2.5.5 is vulnerable to Broken Access Control","id":"CVE-2023-48751","kev_date_added":null,"published":"2023-12-18"},{"cvss_score":4.3,"headline":"WordPress Participants Database Plugin \u003c= 2.4.5 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2022-47612","kev_date_added":null,"published":"2023-02-28"}],"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 exploit SQL injection in the Participants Database plugin to exfiltrate data and potentially execute code.","url":"https://insights.sbomify.com/CVE-2020-8596/"}