CVE-2026-40483
Stored XSS in ChurchCRM Pledge Editor via Unescaped Input
Publication date: 2026-04-18
Last updated on: 2026-04-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| churchcrm | churchcrm | to 7.2.0 (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. |
| CWE-116 | The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in ChurchCRM versions prior to 7.2.0 in the Pledge Editor component. An authenticated user with Finance permissions can inject malicious HTML attribute-breaking characters and event handlers into the donation comment field. These injected values are stored in the database and later executed in the browser of any user who opens the pledge record for editing. This results in a stored Cross-Site Scripting (XSS) attack.
How can this vulnerability impact me? :
The vulnerability allows an attacker with Finance permissions to execute stored XSS attacks. This means malicious scripts can run in the browsers of users who view or edit the affected pledge records, potentially leading to unauthorized actions, data theft, session hijacking, or other malicious activities within the ChurchCRM application.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade ChurchCRM to version 7.2.0 or later, where the issue has been fixed.
Additionally, restrict Finance permissions to trusted users only, as the vulnerability requires authenticated users with these permissions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in ChurchCRM allows an authenticated user with Finance permissions to inject malicious HTML and JavaScript code into donation comment fields, which can execute in the browsers of other users. This stored cross-site scripting (XSS) flaw can lead to unauthorized actions or data exposure within the application.
Such vulnerabilities can impact compliance with common standards and regulations like GDPR and HIPAA because they may lead to unauthorized access or disclosure of personal or sensitive data, violate data protection principles, and undermine the security controls required by these regulations.
Therefore, until fixed (in version 7.2.0), this vulnerability could pose a risk to maintaining compliance with these standards due to potential data integrity and confidentiality issues.