Cyber Resilience

CVE-2026-39341

HighPublic PoC

Published: 07 April 2026

Published
07 April 2026
Modified
15 April 2026
KEV Added
Patch
CVSS Score v3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0028 19.6th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-39341 is a high-severity SQL Injection (CWE-89) vulnerability in Churchcrm Churchcrm. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 19.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).

Deeper analysis

CVE-2026-39341 is a time-based SQL injection vulnerability (CWE-89) affecting ChurchCRM, an open-source church management system, in versions prior to 7.1.0. The issue stems from improper input validation in the endpoint Reports/ConfirmReportEmail.php?familyId=, where user input is sanitized but the sanitized version is not used when constructing the SQL query. This flaw has a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), indicating high severity due to its potential for remote exploitation with low privileges.

A low-privileged remote attacker can exploit this vulnerability over the network with low complexity and no user interaction required. By injecting malicious payloads into the familyId parameter, the attacker can manipulate SQL queries to extract sensitive data from the database (high confidentiality impact) or modify database contents (high integrity impact), though availability is unaffected.

The ChurchCRM security advisory at https://github.com/ChurchCRM/CRM/security/advisories/GHSA-3h69-vjff-jj5c confirms the vulnerability and states it is fixed in version 7.1.0, recommending users upgrade to this release or later to mitigate the issue through proper input sanitization in the affected endpoint.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability details

ChurchCRM is an open-source church management system. Prior to 7.1.0, the application is vulnerable to time-based SQL injection due to an improper input validation. Endpoint Reports/ConfirmReportEmail.php?familyId= is not correctly sanitising user input, specifically, the sanitised input is not used to…

more

create the SQL query. This vulnerability is fixed in 7.1.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

SQL injection in a web application endpoint (Reports/ConfirmReportEmail.php) allows remote network exploitation of the public-facing ChurchCRM system by low-privileged attackers, directly mapping to T1190: Exploit Public-Facing Application.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-39334Same product: Churchcrm Churchcrm
CVE-2026-39330Same product: Churchcrm Churchcrm
CVE-2026-39327Same product: Churchcrm Churchcrm
CVE-2026-39326Same product: Churchcrm Churchcrm
CVE-2026-39318Same product: Churchcrm Churchcrm
CVE-2026-39342Same product: Churchcrm Churchcrm
CVE-2025-1132Same product: Churchcrm Churchcrm
CVE-2026-39325Same product: Churchcrm Churchcrm
CVE-2026-39319Same product: Churchcrm Churchcrm
CVE-2026-39340Same product: Churchcrm Churchcrm

Affected Assets

churchcrm
churchcrm
≤ 7.1.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires proper validation of user inputs such as the familyId parameter to prevent time-based SQL injection attacks.

prevent

Mandates timely identification, reporting, and correction of flaws like this SQL injection vulnerability through patching to version 7.1.0 or later.

detectrespond

Vulnerability scanning would detect SQL injection flaws in endpoints like Reports/ConfirmReportEmail.php and trigger remediation.

References