dbcve.org
ChurchcrmApplication

CVE-2026-39319

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

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, a second order SQL injection vulnerability was found in the endpoint /FundRaiserEditor.php in ChurchCRM. A user has to be authenticated but doesn't need any privileges. These users can inject arbitrary SQL statements through the iCurrentFundraiser PHP session parameter and thus extract and modify information from the database. 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

A second-order SQL injection vulnerability exists in ChurchCRM's /FundRaiserEditor.php endpoint. Authenticated users (without special privileges) can inject arbitrary SQL statements through the iCurrentFundraiser PHP session parameter. The injected payload is stored and later executed when the session value is used in a database query, allowing attackers to extract or modify database contents.

MitigationUpgrade ChurchCRM to version 7.1.0 or later. If immediate upgrade is not possible, implement input validation/sanitization on the iCurrentFundraiser session parameter and restrict database privileges for the application user to limit the impact of potential exploitation.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify ChurchCRM installation and version
    Locate the ChurchCRM installation directory and check the version file or header files for the installed version number. Common locations include the root directory or a version.php file.
    Affected if The installed version is lower than 7.1.0
  2. Verify FundRaiserEditor.php endpoint exists
    Check for the presence of FundRaiserEditor.php in the web application's source code directory.
    Affected if The FundRaiserEditor.php file exists in the application and is accessible via web request
  3. Check session parameter usage
    Examine the FundRaiserEditor.php source code to confirm it references or uses the iCurrentFundraiser session variable in database queries.
    Affected if The code retrieves and uses $_SESSION['iCurrentFundraiser'] in SQL queries without proper sanitization
  4. Verify PHP session handling is active
    Confirm that PHP session management is enabled and that users can establish authenticated sessions in the application.
    Affected if The application uses PHP sessions and allows authenticated user access to the FundRaiserEditor functionality

A user is affected if ChurchCRM version is below 7.1.0 AND the FundRaiserEditor.php endpoint is present and uses the iCurrentFundraiser session parameter in database queries without sanitization.

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 ChurchCRM to version 7.1.0 or later. If immediate upgrade is not possible, implement input validation/sanitization on the iCurrentFundraiser session parameter and restrict database privileges for the application user to limit the impact of potential exploitation.

Recommended fix High confidence

ChurchCRM 7.1.0

  1. Backup your current ChurchCRM database and files before upgrading
  2. Download ChurchCRM version 7.1.0 from the official GitHub releases or repository
  3. Replace the existing ChurchCRM files with the new version 7.1.0 files
  4. Run any database migration scripts included in the 7.1.0 release if applicable
  5. Verify the /FundRaiserEditor.php endpoint is updated and no longer vulnerable
  6. Test that the application functions normally after the upgrade

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

Fix this in Churchcrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39319 — 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-39319 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