{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1132 exists.","fix":"No fix has been published for CVE-2025-1132 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1132 is a critical SQL injection vulnerability in Churchcrm Churchcrm, published on 19 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-1132 and fix it if it is affected.\n\nWhat it is: CVE-2025-1132 is a critical SQL injection vulnerability in Churchcrm Churchcrm, published on 19 Feb 2025. 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-2025-1132 exists.\n\nAffected product: Churchcrm Churchcrm. 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-2025-1132/ (Markdown: https://insights.sbomify.com/CVE-2025-1132/index.md)","id":"CVE-2025-1132","markdown":"https://insights.sbomify.com/CVE-2025-1132/index.md","name":"CVE-2025-1132","record":{"aliases":["GHSA-32xx-6c3g-hvfm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ChurchCRM","requires_auth":"high_privilege","summary":"An authenticated administrator can exploit a time-based blind SQL injection in ChurchCRM to retrieve sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Gridware","cpe":[{"product":"churchcrm","vendor":"churchcrm"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:H/AU:Y/R:U/V:C/RE:H/U:Red","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A time-based blind SQL Injection vulnerability exists in the ChurchCRM 5.13.0 and prior EditEventAttendees.php within the EN_tyid parameter. The parameter is directly inserted into an SQL query without proper sanitization, allowing attackers to inject malicious SQL commands. Please note that the vulnerability requires Administrator permissions. This flaw can potentially allow attackers to delay the response, indicating the presence of an SQL injection vulnerability. While it is a time-based blind injection, it can be exploited to gain insights into the underlying database, and with further exploitation, sensitive data could be retrieved.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SQL Injection in ChurchCRM EN_tyid Parameter via EditEventAttendees.php","id":"CVE-2025-1132","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"churchcrm:churchcrm","products":["churchcrm:churchcrm"],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL Injection in ChurchCRM EID Parameter via EditEventAttendees.php","id":"CVE-2025-1133"},"packages":[],"prev":{"headline":"Asterisk Unsafe Shell Sourcing in safe_asterisk Leads to Local Privilege Escalation","id":"CVE-2025-1131"},"products":["ChurchCRM"],"published":"2025-02-19","related":[{"cvss_score":10,"headline":"ChurchCRM Affected by Unauthenticated RCE in Install Wizard","id":"CVE-2026-39337","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":10,"headline":"ChurchCRM has unauthenticated RCE in its Install Wizard","id":"CVE-2025-62521","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":10,"headline":"ChurchCRM discloses database information on error message","id":"CVE-2025-68110","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-53438","kev_date_added":null,"published":"2024-11-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25894","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25897","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":9.6,"headline":"ChurchCRM has SQL injection in EditEventAttendees.php","id":"CVE-2025-68112","kev_date_added":null,"published":"2025-12-17"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-19","vendors":["ChurchCRM"]},"summary":"An authenticated administrator can exploit a time-based blind SQL injection in ChurchCRM to retrieve sensitive database information.","url":"https://insights.sbomify.com/CVE-2025-1132/"}