CVE-2026-35575
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedChurchCRM 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 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceChurchCRM versions prior to 6.5.3 contain a stored XSS vulnerability in the admin panel's group-creation feature. Users with group-creation privileges can inject malicious JavaScript payloads into group fields that persist on the server. When administrators subsequently view the affected group pages, the embedded script executes automatically, enabling theft of administrator session cookies and potential full administrative account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.5.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed ChurchCRM versionAccess the admin panel and locate the version information (typically found in About or System Settings page), or check the version file in the ChurchCRM installation directoryAffected if The displayed version number is less than 6.5.3 (for example, 6.5.0, 6.5.1, 6.5.2, or any version starting with 6.x below 6.5.3)
-
Verify group-creation privilege assignmentIn the admin panel, navigate to User Management or Permissions settings and review which users or roles have group-creation or group-management capabilitiesAffected if Any user account other than the primary administrator has been granted group-creation privileges, as this creates the attack surface for the XSS injection
-
Inspect existing groups for suspicious contentAccess the group management or groups list in the admin panel and examine group names, descriptions, and other custom fields for any unusual characters, HTML tags, or script elements (for example, <script>, javascript:, onload=, or similar patterns)Affected if Any group entry contains JavaScript code, HTML tags, or encoded payloads that did not originate from your organization, indicating potential prior exploitation
You are affected if your ChurchCRM installation shows a version below 6.5.3 AND users with group-creation privileges exist in your system, or if malicious scripts are already present in your group data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.5.3
Upgrade ChurchCRM to version 6.5.3 or later to obtain the security fix. In the interim, restrict group-creation privileges to highly trusted users and monitor admin sessions for anomalous activity.
6.5.3
- 1. Backup your ChurchCRM database and all application files before proceeding with the upgrade
- 2. Download ChurchCRM version 6.5.3 from the official GitHub releases page (github.com/ChurchCRM/CRM/releases)
- 3. Extract the new version files to your web server document root, replacing the existing installation
- 4. Run any database migration scripts included in the upgrade (check the release notes for specific instructions)
- 5. Clear any application caches if applicable
- 6. Verify the upgrade was successful by logging into the ChurchCRM admin panel
- 7. Test the group creation feature in the admin panel to confirm the XSS vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35575 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data