CVE-2025-68400 ChurchCRM vulnerable to time-based blind SQL Injection in ConfirmReportEmail.php

Critical 9.3 Published Updated

Authenticated users can exploit SQL injection in a legacy endpoint to read or modify database contents.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-68400?

CVE-2025-68400 is a critical SQL injection vulnerability in Churchcrm Churchcrm, published on 17 Dec 2025. 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. A SQL Injection vulnerability exists in the legacy endpoint `/Reports/ConfirmReportEmail.php` in ChurchCRM prior to version 6.5.3. Although the feature was removed from the UI, the file remains deployed and reachable directly via URL. This is a classic case of *dead but reachable code*. Any authenticated user - including one with zero assigned permissions - can exploit SQL injection through the `familyId` parameter. Version 6.5.3 fixes the issue.

Weakness: CWE-89

Which versions are affected by CVE-2025-68400?

It affects 1 product.

Products include Churchcrm Churchcrm.

How do I fix CVE-2025-68400?

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

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is CVE-2025-68400 being exploited?

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

Public exploit code: 1 proofs of concept on GitHub.

All Churchcrm Churchcrm vulnerabilities

Sources

Also known as GHSA-v54g-2pvg-gvp2.

Is CVE-2025-68400 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free