{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68399 exists.","fix":"No fix has been published for CVE-2025-68399 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68399 is a low-severity cross-site scripting vulnerability in Churchcrm Churchcrm, published on 17 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-68399 and fix it if it is affected.\n\nWhat it is: CVE-2025-68399 is a low-severity cross-site scripting vulnerability in Churchcrm Churchcrm, published on 17 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68399 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-68399/ (Markdown: https://insights.sbomify.com/CVE-2025-68399/index.md)","id":"CVE-2025-68399","markdown":"https://insights.sbomify.com/CVE-2025-68399/index.md","name":"CVE-2025-68399","record":{"aliases":["GHSA-gfxf-w4cg-c54j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Church management system","requires_auth":"low_privilege","summary":"Attackers with group modification permissions can inject malicious scripts into ChurchCRM, potentially compromising user sessions and data.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"churchcrm","vendor":"churchcrm"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"ChurchCRM is an open-source church management system. In versions prior to 6.5.4, there is a Stored Cross-Site Scripting (XSS) vulnerability within the GroupEditor.php page of the application. When a user attempts to create a group role, they can execute malicious JavaScript. However, for this to work, the user must have permission to view and modify groups in the application. Version 6.5.4 fixes the issue.","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":"ChurchCRM has Stored Cross-Site Scripting (XSS) In GroupEditor.php","id":"CVE-2025-68399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"churchcrm:churchcrm","products":["churchcrm:churchcrm"],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"ChurchCRM vulnerable to time-based blind SQL Injection in ConfirmReportEmail.php","id":"CVE-2025-68400"},"packages":[],"prev":{"headline":"Weblate has git config file overwrite vulnerability that leads to remote code execution","id":"CVE-2025-68398"},"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-18","vendors":["ChurchCRM"]},"summary":"Attackers with group modification permissions can inject malicious scripts into ChurchCRM, potentially compromising user sessions and data.","url":"https://insights.sbomify.com/CVE-2025-68399/"}