dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-42288

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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.3.2, The fix for CVE-2026-39337 is incomplete. The pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard via unsanitized DB_PASSWORD remains fully exploitable This vulnerability is fixed in 7.3.2.

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.3.2 contain a pre-authentication remote code execution vulnerability in the setup wizard. The issue stems from an unsanitized DB_PASSWORD parameter that allows attackers to execute arbitrary code before any authentication occurs. This CVE represents an incomplete fix of a previously reported vulnerability (CVE-2026-39337), leaving the RCE vector fully exploitable.

MitigationUpgrade ChurchCRM to version 7.3.2 or later immediately, as this is a pre-authentication RCE with CVSS 10 critical severity requiring no authentication to exploit.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Locate ChurchCRM installation
    Search for ChurchCRM files in web server document roots (e.g., /var/www/html, /opt/lampp/htdocs, C:\inetpub\wwwroot) or check for churchcrm directories.
    Affected if ChurchCRM is present on the system.
  2. Determine installed version
    Open the Version.php or similar version file in the ChurchCRM root directory, or check the login page source for version information. Compare the version number to 7.3.2.
    Affected if The installed version is lower than 7.3.2.
  3. Check if setup wizard is accessible
    Attempt to access the setup wizard endpoint (typically /setup or /install) via HTTP/HTTPS from a browser or curl command. Look for the database configuration page.
    Affected if The setup wizard page loads and accepts input, indicating it has not been disabled or is still accessible.
  4. Inspect setup database configuration
    If setup wizard is accessible, examine the DB_PASSWORD field input in the database configuration form. The vulnerability exists if this parameter is not sanitized before being used in system command execution.
    Affected if The DB_PASSWORD parameter in the setup wizard accepts arbitrary input without sanitization and is used in a way that allows code execution.

A system is affected if it runs ChurchCRM version lower than 7.3.2 AND the setup wizard remains accessible, allowing unauthenticated attackers to inject code via the DB_PASSWORD parameter.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ChurchCRM to version 7.3.2 or later immediately, as this is a pre-authentication RCE with CVSS 10 critical severity requiring no authentication to exploit.

Recommended fix High confidence

ChurchCRM 7.3.2

  1. 1. Back up your existing ChurchCRM installation including database and configuration files
  2. 2. Download ChurchCRM version 7.3.2 from the official GitHub repository (https://github.com/ChurchCRM/CRM/releases)
  3. 3. Replace the existing ChurchCRM files with the new version 7.3.2 files
  4. 4. Restore your configuration file and database connection settings
  5. 5. Verify the installation by accessing the setup wizard and confirming the version displays as 7.3.2
  6. 6. Test critical functionality to ensure the upgrade did not break existing features
  7. 7. Ensure the DB_PASSWORD field in the setup wizard now properly sanitizes input to prevent code injection
Caveat Review release notes for any configuration changes between your current version and 7.3.2; test in staging before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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