CVE-2025-68275
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-17

Last updated on: 2025-12-18

Assigner: GitHub, Inc.

Description
ChurchCRM is an open-source church management system. Versions prior to 6.5.3 have a stored cross-site scripting vulnerability on the pages `View Active People`, `View Inactive people`, and `View All People`. Version 6.5.3 fixes the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-17
Last Modified
2025-12-18
Generated
2026-06-16
AI Q&A
2025-12-18
EPSS Evaluated
2026-06-14
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
churchcrm churchcrm to 6.5.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Mitigation Strategies

Upgrade ChurchCRM to version 6.5.3 or later, as this version fixes the stored cross-site scripting vulnerability present in earlier versions.

Compliance Impact

The provided resources do not contain information about how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.

Detection Guidance

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]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-68275. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart