{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36674 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36674 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36674 is a high-severity SQL injection vulnerability in n/a, published on 1 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36674 and fix it if it is affected.\n\nWhat it is: CVE-2022-36674 is a high-severity SQL injection vulnerability in n/a, published on 1 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-36674 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-2022-36674/ (Markdown: https://insights.sbomify.com/CVE-2022-36674/index.md)","id":"CVE-2022-36674","markdown":"https://insights.sbomify.com/CVE-2022-36674/index.md","name":"CVE-2022-36674","record":{"aliases":["GHSA-5r3q-54c5-hc9v"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Task Scheduling System","requires_auth":"high_privilege","summary":"SQL injection in Simple Task Scheduling System allows attackers to manipulate database queries via the id parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"simple_task_scheduling_system","vendor":"simple_task_scheduling_system_project"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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":"Simple Task Scheduling System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /schedules/view_schedule.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-2022-36674","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2022-36675"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-36672"},"products":["n/a"],"published":"2022-09-01","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36678","kev_date_added":null,"published":"2022-08-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36679","kev_date_added":null,"published":"2022-08-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36680","kev_date_added":null,"published":"2022-08-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36681","kev_date_added":null,"published":"2022-08-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36682","kev_date_added":null,"published":"2022-08-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36683","kev_date_added":null,"published":"2022-08-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-30927","kev_date_added":null,"published":"2022-06-06"}],"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-03","vendors":["n/a"]},"summary":"SQL injection in Simple Task Scheduling System allows attackers to manipulate database queries via the id parameter.","url":"https://insights.sbomify.com/CVE-2022-36674/"}