CVE-2026-39336
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 issue affects the Directory Reports form fields set from config, Person editor defaults rendered into address fields, and external self-registration form defaults. This is primarily an admin-to-admin stored XSS path where writable configuration fields are abused. 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 · moderate confidenceA stored cross-site scripting (XSS) vulnerability in ChurchCRM versions prior to 7.1.0 allows authenticated administrators to inject malicious scripts through writable configuration fields in Directory Reports, Person editor defaults rendered into address fields, and external self-registration form defaults. The injected payloads persist in configuration storage and execute when other administrators view or interact with these affected components.
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
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N
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 ChurchCRM versionLocate the installed ChurchCRM version number (typically visible in the application footer, about page, or version file) and compare it against 7.1.0Affected if The installed version is anything prior to 7.1.0
-
Verify administrator accessConfirm you are logged in with administrator privileges, as this vulnerability requires an authenticated administrator account to modify configuration fieldsAffected if You have administrator-level access to ChurchCRM
-
Inspect Directory Reports configuration settingsNavigate to the Directory Reports settings area in the ChurchCRM admin panel and examine all writable configuration fields for any injected script tags or suspicious HTML/JavaScript contentAffected if The Directory Reports configuration fields contain unescaped script tags or HTML/javascript attributes
-
Inspect Person editor default valuesLocate the Person editor defaults section in system settings and review all default values that get rendered into address fields for any malicious script contentAffected if Person editor defaults contain script tags or event handlers that would execute when displayed in address contexts
-
Inspect self-registration form defaultsAccess the external self-registration form configuration area and review default field values for any injected JavaScript or HTML that could execute when the form is renderedAffected if Self-registration form defaults contain executable script content
You are affected if running any ChurchCRM version below 7.1.0 and any of the configuration areas (Directory Reports, Person editor defaults, or self-registration form defaults) contain unsanitized script tags or HTML with event handlers that would execute when viewed by other administrators.
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 to obtain the fix. As a defensive measure, review and sanitize existing configuration values in the affected areas (Directory Reports settings, Person editor defaults, and self-registration form defaults) to remove any potentially malicious input.
7.1.0
- 1. Backup your ChurchCRM database and files before upgrading.
- 2. Download ChurchCRM version 7.1.0 from the official GitHub repository (github.com/ChurchCRM/CRM).
- 3. Replace the existing ChurchCRM installation files with the new version 7.1.0 files.
- 4. Run any database migration scripts included in the upgrade (check /Upgrade directory).
- 5. Verify the upgrade was successful by logging into the admin interface.
- 6. Clear any application caches if applicable.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39336 — 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-39336 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