{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7229 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-7229 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-7229 is a critical SQL injection vulnerability in n/a, published on 21 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-2020-7229 and fix it if it is affected.\n\nWhat it is: CVE-2020-7229 is a critical SQL injection vulnerability in n/a, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-7229 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-7229/ (Markdown: https://insights.sbomify.com/CVE-2020-7229/index.md)","id":"CVE-2020-7229","markdown":"https://insights.sbomify.com/CVE-2020-7229/index.md","name":"CVE-2020-7229","record":{"aliases":["GHSA-rpc9-q4wq-9649"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Simplejobscript.com SJS","requires_auth":"none","summary":"Unauthenticated attackers can execute SQL commands via the landing_location parameter in the search engine, potentially accessing or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"simplejobscript","vendor":"simplejobscript"}],"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":"An issue was discovered in Simplejobscript.com SJS before 1.65. There is unauthenticated SQL injection via the search engine. The parameter is landing_location. The function is countSearchedJobs(). The file is _lib/class.Job.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-7229","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":"Information disclosure in n/a","id":"CVE-2020-7231"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-7228"},"products":["n/a"],"published":"2020-01-21","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-8645","kev_date_added":null,"published":"2020-02-06"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-8440","kev_date_added":null,"published":"2020-01-31"},{"cvss_score":8.8,"headline":"Simple Job Script SQL Injection via searched Endpoint","id":"CVE-2019-25498","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.8,"headline":"Simple Job Script SQL Injection via get_job_applications_ajax.php","id":"CVE-2019-25499","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.8,"headline":"Simple Job Script SQL Injection via register-recruiters endpoint","id":"CVE-2019-25500","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.8,"headline":"Simple Job Script SQL Injection via delete_application_ajax.php","id":"CVE-2019-25501","kev_date_added":null,"published":"2026-03-04"}],"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":"Unauthenticated attackers can execute SQL commands via the landing_location parameter in the search engine, potentially accessing or modifying database contents.","url":"https://insights.sbomify.com/CVE-2020-7229/"}