CVE-2026-39334
SQLi in ChurchCRM <=7.0.5 via /SettingsIndividual.php allows DB read/modify.
Is CVE-2026-39334 being exploited?
Not confirmed. CVE-2026-39334 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-39334?
CVE-2026-39334 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-39334?
Yes. A fix has been recorded for CVE-2026-39334. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-39334 affect?
CVE-2026-39334 affects ChurchCRM <= 7.0.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-39334?
Upgrade to 7.1.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated user can inject SQL through type index to read/modify the database.
Patch when possible
- affected< 7.1.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.