How exploitable is this vulnerability in practice?

It can be highly exploitable when the endpoint is reachable by untrusted users and the database responds consistently to time-based probes. Even without direct data error messages, attackers can infer data via response timing differences.

Does an attacker need authenticated access to exploit this?

That depends on how the ChurchCRM instance is configured. If `Reports/ConfirmReportEmail.php` is accessible without strong authentication or is exposed to lower-privileged users, those users could exploit the vulnerability.

What is the safest general fix pattern for this issue?

The safest pattern is to refactor the vulnerable code to use parameterized queries or prepared statements exclusively, passing only typed, validated parameters into the SQL layer and avoiding any string concatenation of user input.

Severity:

HIGH RISK

(8.1)

Time-Based SQL Injection (CWE-89) in ChurchCRM Confirm Report Email Endpoint

CVE-2026-39341

Published:

Apr 7, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Data Exfiltration and Integrity Compromise via SQL Injection

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Data Exfiltration and Integrity Compromise via SQL Injection

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Time-Based SQL Injection (CWE-89) in ChurchCRM Confirm Report Email Endpoint

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal