ChurchCRM has Stored XSS in PersonView.php via Facebook Field Attribute Injection

published 2026-04-07 7 mo ago modified 2026-10-26 13 d ago also EUVD-2026-19718

cvss: 7.6; 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 6%
public exploits: 0; none known

ChurchCRM is an open-source church management system. Prior to 7.1.0, a stored cross-site scripting vulnerability exists in PersonView.php due to incorrect use of sanitizeText() as an output sanitizer for HTML attribute context. The function only strips HTML tags, it does not escape quote characters allowing an attacker to break out of the href attribute and inject arbitrary JavaScript event handlers. Any authenticated user with the EditRecords role can store the payload in a person's Facebook field. The XSS fires against any user who views that person's profile page, including administrators, enabling session hijacking and full account takeover. This vulnerability is fixed in 7.1.0.

Patch / fix

fixed in 1

churchcrm churchcrm 7.1.0

CISA SSVC

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

Exploit prediction

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

Exploits and checks

github.com https://github.com/ChurchCRM/CRM/security/advisories/GHSA-pqp6-54p2-m66f referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

ChurchCRM CRM

Classification

Weakness

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

References

github.com /ChurchCRM/CRM/security/advisories/GHSA-pqp6-54p2-m66f
exploit, third-party-advisory

Sources

CVE List CVE-2026-35534
NVD CVE-2026-35534

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.

Summary