Quick answers
- Is CVE-2026-42288 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42288 being exploited in the wild.
- How severe is CVE-2026-42288?
- Critical severity, with a CVSS score of 10, published 12 May 2026.
- Which products and versions are affected?
- ChurchCRM Prior to 7.3.2.
- Is there a fix for CVE-2026-42288?
- A patch was published on 2026-05-12: Fixed in version 7.3.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42288 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-42288?
- Check whether you run ChurchCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
ChurchCRM is vulnerable to remote code execution (RCE) because the setup wizard fails to sanitize the 'DB_PASSWORD' input field in 'src/setup/routes/setup.php'. This field is directly substituted into a single-quoted PHP string within the 'Config.php.example' template. An unauthenticated attacker can provide a payload that breaks out of the string literal (e.g., using single quotes) and injects PHP functions like 'shell_exec()'. The malicious code is executed when 'Config.php' is subsequently loaded by the application, typically on the next request to the index page. This vulnerability persists because a previous fix (CVE-2026-39337) failed to address the password field specifically. The issue is resolved in version 7.3.2.
Affected products
- ChurchCRM ChurchCRM Prior to 7.3.2
Timeline
- 2026-05-12: disclosed
- 2026-05-12: advisory
- 2026-05-12: patched: Fixed in version 7.3.2