{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68400 exists.","fix":"No fix has been published for CVE-2025-68400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68400 is a critical SQL injection vulnerability in Churchcrm Churchcrm, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68400 and fix it if it is affected.\n\nWhat it is: CVE-2025-68400 is a critical SQL injection vulnerability in Churchcrm Churchcrm, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68400 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-68400/ (Markdown: https://insights.sbomify.com/CVE-2025-68400/index.md)","id":"CVE-2025-68400","markdown":"https://insights.sbomify.com/CVE-2025-68400/index.md","name":"CVE-2025-68400","record":{"aliases":["GHSA-v54g-2pvg-gvp2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ChurchCRM","requires_auth":"none","summary":"Authenticated users can exploit SQL injection in a legacy endpoint to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"churchcrm","vendor":"churchcrm"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"ChurchCRM is an open-source church management system. A SQL Injection vulnerability exists in the legacy endpoint `/Reports/ConfirmReportEmail.php` in ChurchCRM prior to version 6.5.3. Although the feature was removed from the UI, the file remains deployed and reachable directly via URL. This is a classic case of *dead but reachable code*. Any authenticated user - including one with zero assigned permissions - can exploit SQL injection through the `familyId` parameter. Version 6.5.3 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-04-11","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-11T19:13:20Z","kind":"github_poc","ref":"https://github.com/lukasz-rybak/CVE-2025-68400","stars":0,"title":"CVE-2025-68400 - ChurchCRM vulnerable to time-based blind SQL Injection in ConfirmReportEmail.php"}],"tier":"weaponised"},"has_fix":false,"headline":"ChurchCRM vulnerable to time-based blind SQL Injection in ConfirmReportEmail.php","id":"CVE-2025-68400","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":"ChurchCRM has Stored Cross-Site Scripting (XSS) vulnerability that leads to session theft and account takeover","id":"CVE-2025-68401"},"packages":[],"prev":{"headline":"ChurchCRM has Stored Cross-Site Scripting (XSS) In GroupEditor.php","id":"CVE-2025-68399"},"products":["CRM"],"published":"2025-12-17","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-18","vendors":["ChurchCRM"]},"summary":"Authenticated users can exploit SQL injection in a legacy endpoint to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2025-68400/"}