CVE-2026-39328
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 7.1.0, a stored cross-site scripting vulnerability exists in ChurchCRM's person profile editing functionality. Non-administrative users who have the EditSelf permission can inject malicious JavaScript into their Facebook, LinkedIn, and X profile fields. Due to a 50-character field limit, the payload is distributed across all three fields and chains their onfocus event handlers to execute in sequence. When any user, including administrators, views the attacker's profile, their session cookies are exfiltrated to a remote server. This vulnerability is fixed in 7.1.0.
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 confidenceA stored cross-site scripting (XSS) vulnerability in ChurchCRM versions prior to 7.1.0 allows non-administrative users with EditSelf permission to inject malicious JavaScript into Facebook, LinkedIn, and X profile fields. Due to a 50-character field limit, attackers distribute their payload across all three fields, chaining onfocus event handlers to achieve execution. When any user views the compromised profile, the attacker's script exfiltrates session cookies to a remote server.
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< 7.1.0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L
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.
-
Identify installed ChurchCRM versionCheck the application footer, navigate to the admin panel version info, or locate and read the version file in the includes directory to determine the exact version numberAffected if If the installed version is earlier than 7.1.0, the system falls within the vulnerable range
-
Determine if EditSelf permission is activeIn the ChurchCRM administration panel, access User Management or Permissions settings and review which users or user roles have the EditSelf permission enabledAffected if If non-administrative users have EditSelf permission, the exploit condition is present in the environment
-
Examine profile social media fields for malicious contentAccess the database person_custom table or view user profiles through the web interface and inspect the Facebook, LinkedIn, and X (Twitter) fields for onfocus event handlers, script tags, or unusual encoded character sequences that could indicate XSS payloadsAffected if If any of these three fields contain onfocus attributes or JavaScript code, the system is likely compromised
A system is affected if it runs ChurchCRM version earlier than 7.1.0, non-administrative users have EditSelf permission, and any user profile contains suspicious script content in the social media fields.
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 · scoped7.1.0
Upgrade to ChurchCRM version 7.1.0 or later, which includes the fix. Additionally, implement proper input validation and output encoding for all user-supplied profile fields to prevent XSS.
7.1.0
- Back up the current ChurchCRM installation and database before proceeding with the upgrade
- Download ChurchCRM version 7.1.0 from the official GitHub repository or release page
- Follow the official ChurchCRM upgrade documentation for your current version to install version 7.1.0
- After upgrading, verify that the Facebook, LinkedIn, and X profile fields properly sanitize input
- Test that the profile viewing functionality no longer executes injected JavaScript from these fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39328 — 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-39328 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