CVE-2026-39344
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, there is a Reflected Cross-Site Scripting (XSS) vulnerability on the login page, which is caused by the lack of sanitization or encoding of the username parameter received from the URL. The username parameter value is directly displayed in the login page input element without filter, allowing attackers to insert malicious JavaScript scripts. If successful, script can be executed on the client side, potentially stealing sensitive data such as session cookies or replacing the display to show the attacker's login form. 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 confidenceChurchCRM versions prior to 7.1.0 contain a reflected XSS vulnerability in the login page where the username parameter from the URL is directly rendered in the input field without sanitization or encoding, allowing injection of malicious JavaScript.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify ChurchCRM installation locationLook for ChurchCRM files in the web server document root, typically under /churchcrm, /crm, or similar directories. Check for the presence of files such as index.php, login.php, or a Include/Config.php file that contains 'ChurchCRM' references.Affected if ChurchCRM is not found on the system - not applicable if the product is not present
-
Determine installed ChurchCRM versionCheck the ChurchCRM version file or system. Common locations: /Include/Config.php may contain version info, or look for a version.php file in the Include or root directory. The version may also be visible in the page source of the login page footer.Affected if The installed version number cannot be determined or is lower than 7.1.0
-
Access the ChurchCRM login pageNavigate to the ChurchCRM login URL (typically /login.php or /index.php) on the web server to confirm the application is running and accessible.Affected if The login page is not accessible - not affected if the application is not running
-
Compare version to affected rangeIf you found a version number in step 2, compare it against the affected range: versions prior to 7.1.0. Any version 7.0.x, 6.x, or earlier are within the affected range.Affected if The installed version is 7.0.x, 6.x, or any version number less than 7.1.0
A system is affected if ChurchCRM is installed and the identified version is lower than 7.1.0, as this version range contains the unsanitized username parameter vulnerability on the login page.
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 proper input sanitization for the username parameter.
7.1.0
- Backup your existing ChurchCRM database and files before upgrading
- Download ChurchCRM version 7.1.0 from the official GitHub repository or releases page
- Follow the standard ChurchCRM upgrade procedure for your deployment method (manual or package-based)
- Replace all existing application files with the new version 7.1.0 files
- Run any database migration scripts included in the 7.1.0 release if applicable
- Clear any cached data and session files
- Verify the login page no longer reflects the username parameter without sanitization
- Confirm normal login functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39344 — 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-39344 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