dbcve.org
ChurchcrmApplication

CVE-2026-39333

HIGH · 8.7 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable

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 · unedited
ChurchCRM is an open-source church management system. Prior to 7.1.0, he FindFundRaiser.php endpoint reflects user-supplied input (DateStart and DateEnd) into HTML input field attributes without proper output encoding for the HTML attribute context. An authenticated attacker can craft a malicious URL that executes arbitrary JavaScript when visited by another authenticated user. This constitutes a reflected XSS vulnerability. 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 confidence

ChurchCRM versions prior to 7.1.0 contain a reflected XSS vulnerability in the FindFundRaiser.php endpoint. The DateStart and DateEnd parameters are reflected into HTML input field attributes without proper output encoding for the HTML attribute context, allowing authenticated attackers to inject arbitrary JavaScript via crafted URLs.

MitigationUpgrade to ChurchCRM version 7.1.0 or later, which implements proper output encoding for the DateStart and DateEnd parameters in HTML attribute context.

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
ChurchcrmApplication
Affected:< 7.1.0

CVSS 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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ChurchCRM installation
    Locate the ChurchCRM application directory or check your web server for the ChurchCRM application files
    Affected if ChurchCRM is installed on the server
  2. Identify installed ChurchCRM version
    Check the version number of your ChurchCRM installation - typically found in the application header, footer, or in a version file within the installation directory
    Affected if The installed version is anything prior to 7.1.0 (e.g., 7.0.x, older releases)
  3. Locate FindFundRaiser.php endpoint
    Search for the FindFundRaiser.php file within the ChurchCRM web directory
    Affected if The file exists and is accessible via the web server
  4. Verify parameter reflection in HTML attributes
    Access the FindFundRaiser.php endpoint with test values in the DateStart and DateEnd parameters, then view the page source to inspect how these values are rendered in HTML input field attributes
    Affected if The DateStart or DateEnd values appear unencoded in HTML attribute context (e.g., within value="" attributes)
  5. Confirm authentication requirements
    Attempt to access the FindFundRaiser.php endpoint to determine if authentication is required
    Affected if The endpoint is accessible to authenticated users only, meaning an attacker needs valid credentials to exploit the XSS

Your environment is affected if ChurchCRM versions prior to 7.1.0 are installed and the FindFundRaiser.php endpoint with unencoded DateStart/DateEnd parameters in HTML attributes is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.1.0 or later
Fixed in 7.1.0
Interim mitigation

Upgrade to ChurchCRM version 7.1.0 or later, which implements proper output encoding for the DateStart and DateEnd parameters in HTML attribute context.

Recommended fix High confidence

ChurchCRM 7.1.0

  1. Verify current ChurchCRM version by checking the admin dashboard or system information page
  2. Backup the current ChurchCRM database and files before upgrading
  3. Download ChurchCRM version 7.1.0 from the official GitHub releases page (github.com/ChurchCRM/CRM)
  4. Extract the new version files to replace the existing installation
  5. Run any database migration scripts included in the 7.1.0 release
  6. Verify the upgrade was successful by logging into the admin panel
  7. Confirm the FindFundRaiser.php page now properly encodes DateStart and DateEnd parameters in HTML attribute context

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Churchcrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39333 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39333 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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