CVE-2026-40483
Received Received - Intake
Stored XSS in ChurchCRM Pledge Editor via Unescaped Input

Publication date: 2026-04-18

Last updated on: 2026-04-18

Assigner: GitHub, Inc.

Description
ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the Pledge Editor renders donation comment values directly into HTML input value attributes without escaping via htmlspecialchars(). An authenticated user with Finance permissions can inject HTML attribute-breaking characters and event handlers into the comment field, which are stored in the database and execute in the browser of any user who subsequently opens the pledge record for editing, resulting in stored XSS. This issue has been fixed in version 7.2.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-18
Last Modified
2026-04-18
Generated
2026-06-16
AI Q&A
2026-04-18
EPSS Evaluated
2026-06-15
NVD
CVE-2026-40483
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
churchcrm churchcrm to 7.2.0 (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.
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Mitigation Strategies

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.

Compliance Impact

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.

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