CVE-2025-68275
BaseFortify
Publication date: 2025-12-17
Last updated on: 2025-12-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| churchcrm | churchcrm | to 6.5.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stored cross-site scripting (XSS) issue in ChurchCRM versions prior to 6.5.3. It occurs on the pages 'View Active People', 'View Inactive People', and 'View All People'. Malicious scripts can be stored and executed when users visit these pages, potentially compromising user data or session information.
How can this vulnerability impact me? :
The stored cross-site scripting vulnerability can allow attackers to execute malicious scripts in the context of the affected application. This can lead to unauthorized actions, theft of sensitive information, session hijacking, or other malicious activities that compromise the security and integrity of the system and its users.
What immediate steps should I take to mitigate this vulnerability?
Upgrade ChurchCRM to version 6.5.3 or later, as this version fixes the stored cross-site scripting vulnerability present in earlier versions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information about how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the ChurchCRM instance is running a version prior to 6.5.3 and by testing the group name input field for stored XSS payloads. One approach is to attempt injecting a harmless script payload (e.g., <script>alert('XSS')</script>) into the group name field and then viewing the pages 'View Active People', 'View Inactive People', or 'View All People' to see if the script executes. Additionally, scanning for the presence of known vulnerable versions can be done by querying the application version. Specific commands depend on your environment, but for example, using curl to check the version or to submit a test payload via HTTP POST to the group creation endpoint can be used. However, no explicit commands are provided in the resources. [1]