ChurchCRM: Stored XSS in PledgeEditor.php via Donation Comment Field

published 2026-04-17 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-23595

cvss: 5.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 2

churchcrm churchcrm 7.2.0

github.com/ChurchCRM/CRM@b3da72a commit
github.com/ChurchCRM/CRM#8609 pull request

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 6 mo ago (2026-04-20)

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected products

ChurchCRM CRM

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation
CWE-116 Improper Encoding or Escaping of Output

References

Sources

CVE List CVE-2026-40483
NVD CVE-2026-40483

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary