ChurchCRM is an open-source church management system. Versions of the application prior to 5.9.2 are vulnerable to an authenticated SQL injection due to an improper sanitization of user input. Authentication is required, but no elevated privileges are necessary. This allows attackers to inject SQL statements directly into the database query due to inadequate sanitization of the EID parameter in in a GET request to /GetText.php. Version 5.9.2 patches the issue.
CVE-2024-39304
HIGHNVD 8.88.8ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC, other public exploit code (a GitHub or vendor proof of concept, or an Exploit-DB entry not marked verified).First public exploit code on record: 2025-04-09 (Exploit-DB EDB-52152)EchelonGraph confidence 42%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 3.0% (87th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Also known asEUVD-2024-37890 (ENISA EUVD)Source: ENISA EUVD
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 3.0%CVSS: 8.8Exploit: Public PoCExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 56EG Risk 56/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 3.0%
- EPSS %ILE
- 87th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 3.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 26, 2024
Last Modified
November 21, 2024
Advisory Details (2)
Auto-updated Aug 24, 2026Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)
SQLi in ChurchCRM <= 5.8.0 · Advisory · ChurchCRM/CRM · GitHub
https://github.com/ChurchCRM/CRM/security/advisories/GHSA-2rh6-gr3h-83j9GitHub commit Patch Available
commit e3bd7bfbf33f (ChurchCRM/CRM)
Patch available: ChurchCRM/CRM 6.6.1 (contains commit e3bd7bfbf33f)
https://github.com/ChurchCRM/CRM/commit/e3bd7bfbf33f01148df0ef1acdb0cf2c2b878b08Publicly available exploits
(1 shown)Public exploit code is referenced for this CVE (shown: 1 Exploit-DB entry). Defenders should treat patch urgency accordingly.
- Exploit-DBEDB-52152Published Apr 9, 2025
ChurchCRM 5.9.1 - SQL Injection
Open source ↗
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2024-39304?
CVE-2024-39304 is a high-severity vulnerability; its CVE record was published on July 26, 2024. ChurchCRM is an open-source church management system. Versions of the application prior to 5.9.2 are vulnerable to an authenticated SQL injection due to an improper sanitization of user input. Authentication is required, but no elevated privileges are necessary. This allows attackers to inject SQL…
When was the CVE record for CVE-2024-39304 published?
The CVE record for CVE-2024-39304 was published on July 26, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2024-39304 actively exploited?
CVE-2024-39304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-39304?
CVE-2024-39304 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2024-39304?
A fix for CVE-2024-39304 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-39304
Is Your Infrastructure Affected by CVE-2024-39304?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.