# CVE-2026-42288: ChurchCRM: Incomplete fix for CVE-2026-39337: Unauthenticated RCE in Setup Wizard via unsanitized DB_PASSWORD

> Unauthenticated attackers can execute arbitrary code via the setup wizard due to unsanitized database password input in ChurchCRM.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 18 May 2026

## What is CVE-2026-42288?

CVE-2026-42288 is a critical code injection vulnerability in ChurchCRM CRM, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-42288?


## How do I fix CVE-2026-42288?

No fix has been published for CVE-2026-42288 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-42288 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42288 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42288 and fix it if it is affected.

What it is: CVE-2026-42288 is a critical code injection vulnerability in ChurchCRM CRM, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42288 exists.

Affected product: ChurchCRM CRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42288/ (Markdown: https://insights.sbomify.com/CVE-2026-42288/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42288
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42288
- OSV: https://osv.dev/vulnerability/CVE-2026-42288

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42288/
Summaries are generated and may contain mistakes; the official description above is the record.