Cyber Resilience

CVE-2026-35575

XSS in Churchcrm ≤ 6.5.3

XSS
Published
07 April 2026
Modified
09 April 2026
CVSS Score v3.1 8.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0024 16th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2026-35575 is a high-severity Cross-site Scripting (CWE-79) vulnerability in Churchcrm Churchcrm. Its CVSS base score is 8.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-35575 is a Stored Cross-Site Scripting (Stored XSS) vulnerability in ChurchCRM, an open-source church management system, affecting versions prior to 6.5.3. The issue exists in the admin panel’s group-creation feature, where malicious JavaScript can be injected due to inadequate input validation and sanitization. It is associated with CWE-79 (Cross-Site Scripting) and CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag), earning a CVSS v3.1 base score of 8.0 (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H).

Any authenticated user with group-creation privileges can exploit this vulnerability by injecting malicious JavaScript during group creation. The payload is stored and executes automatically in an administrator’s browser when they view the affected page, allowing theft of the administrator’s session cookies and potentially enabling full administrative account takeover.

The vulnerability is fixed in ChurchCRM 6.5.3. Organizations should upgrade to this version or later to mitigate the issue. Additional details are available in the GitHub Security Advisory at https://github.com/ChurchCRM/CRM/security/advisories/GHSA-gc8q-2gw7-qj7w.

OWASP Top 10 for Web (2025)

A02:2025 Security MisconfigurationA05:2025 Injection

EU & UK References

Vulnerability Data

ChurchCRM is an open-source church management system. Prior to 6.5.3, a Stored Cross-Site Scripting (Stored XSS) vulnerability in the admin panel’s group-creation feature allows any user with group-creation privileges to inject malicious JavaScript that executes automatically when an administrator views…

more

the page. This enables attackers to steal the administrator’s session cookies, potentially leading to full administrative account takeover. This vulnerability is fixed in 6.5.3.

CWE(s)
CWE-79CWE-1004

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
attack.mitre.org →
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-26842Same product: Churchcrm Churchcrm
CVE-2023-25346Same product: Churchcrm Churchcrm
CVE-2023-27059Same product: Churchcrm Churchcrm
CVE-2023-31548Same product: Churchcrm Churchcrm
CVE-2023-24686Same product: Churchcrm Churchcrm
CVE-2023-31699Same product: Churchcrm Churchcrm
CVE-2023-38761Same product: Churchcrm Churchcrm
CVE-2023-24690Same product: Churchcrm Churchcrm
CVE-2023-33661Same product: Churchcrm Churchcrm
CVE-2023-26843Same product: Churchcrm Churchcrm

Affected Assets

churchcrm
churchcrm
≤ 6.5.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.

SC-23 Session Authenticity good match

Proper implementation of session authenticity requires marking sensitive session cookies HttpOnly so that client scripts cannot access them.

SI-10 Information Input Validation good match

Input validation directly enforces neutralization of untrusted data before it reaches web output generation.

SI-15 Information Output Filtering good match

Output filtering can catch or sanitize unneutralized script content before it is served to users.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.AT-02 partial match
prevents

Role-based training can reduce the chance developers introduce missing HttpOnly flags but supplies no enforcement or detection, leaving essentially all of the implementation flaw's risk intact.

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

A.5.6 Contact with special interest groups partial match
prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

A.5.7 Threat intelligence partial match
prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

A.8.25 Secure development life cycle partial match
prevents

Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate HttpOnly on sensitive cookies.

A.8.28 Secure coding partial match
prevents

Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.

References