Secuno
ENNL
Book demo

CVE-2025-66313

Churchcrm SQL injection

7.2 HIGHPublic exploitEPSS 0.40%
  1. Published1 Dec 2025

Description

ChurchCRM is an open-source church management system. In ChurchCRM 6.2.0 and earlier, there is a time-based blind SQL injection in the handling of the 1FieldSec parameter. Injecting SLEEP() causes deterministic server-side delays, proving the value is incorporated into a SQL query without proper parameterization. The issue allows data exfiltration and modification via blind techniques.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredHigh
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

Churchcrm≤ 6.2.0

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-891138.8
SAP Commerce Cloud does not sufficiently validate certain user-supplied input before it…
CVE-2026-1096088.8
Frappe ERPNext before 15.121.0 and 16.x before 16.34.0 contains an SQL injection…
CVE-2026-1095738.1
phpMyFAQ before 4.1.9 contains an SQL injection vulnerability in PdoMysql::escape(),…
CVE-2026-893028.6
The Post Voting System WordPress plugin through 1.0 does not properly sanitize and…
CVE-2026-892998.6
The WP Verify API WordPress plugin through 1.0.0 does not properly sanitize and escape…
CVE-2026-892978.6
The Loja Automática WordPress plugin through 1.0.0 does not properly sanitize and…

Frequently asked

Is CVE-2025-66313 being actively exploited?

CVE-2025-66313 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.40%.

How severe is CVE-2025-66313?

CVE-2025-66313 has a CVSS 3.1 base score of 7.2, rated high. EPSS estimates a 0.40% probability of exploitation.

Which products are affected by CVE-2025-66313?

Affected products include Churchcrm.

How do I fix CVE-2025-66313?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-66313 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.