Skip to main content

Churchcrm EUVDEUVD-2026-19772

| CVE-2026-35574 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-04-07 security-advisories@github.com
7.3
CVSS 3.1 · GitHub Advisory
Share

Severity by source

GitHub Advisory PRIMARY
7.3 HIGH
AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

7
Re-analysis Queued
Apr 16, 2026 - 17:52 vuln.today
cvss_changed
Analysis Updated
Apr 16, 2026 - 06:04 EUVD-patch-fix
executive_summary
Re-analysis Queued
Apr 16, 2026 - 05:29 backfill_euvd_patch
patch_released
Patch available
Apr 16, 2026 - 05:29 EUVD
6.5.3
EUVD ID Assigned
Apr 07, 2026 - 17:22 euvd
EUVD-2026-19772
Analysis Generated
Apr 07, 2026 - 17:22 vuln.today
CVE Published
Apr 07, 2026 - 17:16 nvd
HIGH 7.3

DescriptionGitHub Advisory

ChurchCRM is an open-source church management system. Prior to 6.5.3, a stored Cross-Site Scripting (XSS) vulnerability in ChurchCRM's Note Editor allows authenticated users with note-adding permissions to execute arbitrary JavaScript code in the context of other users' browsers, including administrators. This can lead to session hijacking, privilege escalation, and unauthorized access to sensitive church member data. This vulnerability is fixed in 6.5.3.

AnalysisAI

Stored XSS in ChurchCRM Note Editor enables authenticated users to execute arbitrary JavaScript in victims' browsers, leading to session hijacking and privilege escalation against administrators managing sensitive church member data. Affects ChurchCRM versions prior to 6.5.3. CVSS 7.3 (High) reflects network-accessible attack requiring low-privilege authentication and user interaction. EPSS and KEV data not provided; no public exploit identified at time of analysis. Vendor patch released in version 6.5.3.

Technical ContextAI

ChurchCRM is an open-source PHP-based church management system designed for managing membership, donations, and administrative tasks. This vulnerability stems from CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically a stored cross-site scripting flaw in the Note Editor component. The application fails to properly sanitize or encode user-supplied input when rendering notes, allowing malicious JavaScript payloads to persist in the database and execute when other users view the compromised note. The CVSS vector (AV:N/AC:L/PR:L/UI:R) indicates network-accessible exploitation with low complexity, requiring low-privileged authenticated access (any user with note-adding permissions) and victim interaction (admin must view the malicious note). The stored nature makes this particularly dangerous as the payload persists and can affect multiple users over time, unlike reflected XSS which requires per-victim social engineering.

RemediationAI

Upgrade ChurchCRM to version 6.5.3 or later, which contains vendor-released fixes for the stored XSS vulnerability in the Note Editor. Organizations should update immediately by downloading the patched release from the official ChurchCRM GitHub repository. During the upgrade window, implement temporary mitigations including restricting note-adding permissions to only highly trusted administrative users, conducting audit reviews of existing notes for suspicious JavaScript content, and implementing Content Security Policy headers to limit script execution if technically feasible. After upgrading, review user activity logs for any suspicious note modifications that may have occurred prior to patching, as stored XSS payloads could have been injected before the fix was applied. Complete vendor advisory and patch details are available at https://github.com/ChurchCRM/CRM/security/advisories/GHSA-cx82-8xrh-7f5c. Organizations unable to upgrade immediately should consider temporarily disabling the Note Editor feature if operationally feasible until patching can be completed.

CVE-2024-25897 CRITICAL POC
9.8 Feb 21

ChurchCRM 5.5.0 FRCatalog.php is vulnerable to Blind SQL Injection (Time-based) via the CurrentFundraiser GET parameter.

CVE-2024-25894 CRITICAL POC
9.8 Feb 21

ChurchCRM 5.5.0 /EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EventCount POST parameter. Ra

CVE-2025-1023 CRITICAL POC
9.3 Feb 18

A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploit

CVE-2025-1135 CRITICAL POC
9.3 Feb 19

A vulnerability exists in ChurchCRM 5.13.0. Rated critical severity (CVSS 9.3), this vulnerability is remotely exploitab

CVE-2025-1134 CRITICAL POC
9.3 Feb 19

A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploit

CVE-2025-1133 CRITICAL POC
9.3 Feb 19

A vulnerability exists in ChurchCRM 5.13.0 and prior that allows an attacker to execute arbitrary SQL queries by exploit

CVE-2025-1132 CRITICAL POC
9.3 Feb 19

A time-based blind SQL Injection vulnerability exists in the ChurchCRM 5.13.0 and prior EditEventAttendees.php within th

CVE-2024-25893 CRITICAL POC
9.1 Feb 21

ChurchCRM 5.5.0 FRCertificates.php is vulnerable to Blind SQL Injection (Time-based) via the CurrentFundraiser GET param

CVE-2026-24854 HIGH POC
8.8 Jan 30

Authenticated SQL injection in ChurchCRM's PaddleNumEditor.php endpoint prior to version 6.7.2 allows any logged-in user

CVE-2024-39304 HIGH POC
8.8 Jul 26

ChurchCRM is an open-source church management system. Rated high severity (CVSS 8.8), this vulnerability is remotely exp

CVE-2023-29842 HIGH POC
8.8 May 04

ChurchCRM 4.5.4 endpoint /EditEventTypes.php is vulnerable to Blind SQL Injection (Time-based) via the EN_tyid POST para

CVE-2025-1024 HIGH POC
8.4 Feb 19

A vulnerability exists in ChurchCRM 5.13.0 that allows an attacker to execute arbitrary JavaScript in a victim's browser

Share

EUVD-2026-19772 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy