{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41530 exists.","fix":"No fix has been published for CVE-2022-41530 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41530 is a high-severity SQL injection vulnerability in n/a, published on 11 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41530 and fix it if it is affected.\n\nWhat it is: CVE-2022-41530 is a high-severity SQL injection vulnerability in n/a, published on 11 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41530 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-2022-41530/ (Markdown: https://insights.sbomify.com/CVE-2022-41530/index.md)","id":"CVE-2022-41530","markdown":"https://insights.sbomify.com/CVE-2022-41530/index.md","name":"CVE-2022-41530","record":{"aliases":["GHSA-77p8-wh75-m8pf"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SACCO Management System","requires_auth":"high_privilege","summary":"Attackers can exploit SQL injection in the SACCO Management System to read or modify database records via the delete_borrower endpoint.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"open_source_sacco_management_system","vendor":"open_source_sacco_management_system_project"}],"cvss":{"score":7.2,"severity":"high","source":"cisa-adp","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":"Open Source SACCO Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /sacco_shield/ajax.php?action=delete_borrower.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2022-41530","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-41532"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-41528"},"products":["n/a"],"published":"2022-10-11","related":[{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2022-42218","kev_date_added":null,"published":"2022-10-18"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2022-42143","kev_date_added":null,"published":"2022-10-17"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2022-41535","kev_date_added":null,"published":"2022-10-14"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2022-41536","kev_date_added":null,"published":"2022-10-14"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2022-41532","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2022-41514","kev_date_added":null,"published":"2022-10-07"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-19","vendors":["n/a"]},"summary":"Attackers can exploit SQL injection in the SACCO Management System to read or modify database records via the delete_borrower endpoint.","url":"https://insights.sbomify.com/CVE-2022-41530/"}