CVE-2025-66396

HIGHNVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.4% (35th 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
Elevated

Also known asEUVD-2025-203921 (ENISA EUVD)Source: ENISA EUVD

7.2EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

ChurchCRM is an open-source church management system. Prior to version 6.5.3, a SQL injection vulnerability exists in the src/UserEditor.php file. When an administrator saves a user's configuration settings, the keys of the type POST parameter array are not properly sanitized or type-casted before being used in multiple SQL queries. This allows a malicious or compromised administrator account to execute arbitrary SQL commands, including time-based blind SQL injection attacks, to directly interact with the database. The vulnerability is located in src/UserEditor.php within the logic that handles saving user-specific configuration settings. The type parameter from the POST request is processed as an array. The code iterates through this array and uses key($type) to extract the array key, which is expected to be a numeric ID. This key is then assigned to the $id variable. The $id variable is subsequently concatenated directly into a SELECT and an UPDATE SQL query without any sanitization or validation, making it an injection vector. Although the vulnerability requires administrator privileges to exploit, it allows a malicious or compromised admin account to execute arbitrary SQL queries. This can be used to bypass any application-level logging or restrictions, directly manipulate the database, exfiltrate, modify, or delete all data (including other user credentials, financial records, and personal information), and could potentially lead to further system compromise, such as writing files to the server, depending on the database's configuration and user privileges. Version 6.5.3 patches the issue.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity72% × 45%
Impact severity (EG Severity): CVSS 7.2 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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
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 (7.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.

EG Severity
7.2 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
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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.

The CVE record names the fixed release. 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

December 17, 2025

Last Modified

December 18, 2025

Advisory Details (1)

Auto-updated Aug 6, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

SQL Injection in User Editor via `type` Parameter Key · Advisory · ChurchCRM/CRM · GitHub

https://github.com/ChurchCRM/CRM/security/advisories/GHSA-whpp-wx64-4qp9

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 199 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-31 23:23 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-25 16:08 UTCEG score recompute
  12. 2026-10-24 23:13 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-10-18 05:19 UTCEG score recompute
  21. 2026-10-17 23:04 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 70 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-12 16:48 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-11 20:23 UTCEG score recompute
  5. 2026-10-11 18:35 UTCEG score recompute
  6. 2026-10-11 15:10 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-10-03 17:18 UTCOSV refresh
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  27. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  30. 2026-09-14 07:49 UTCOSV refresh
  31. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  32. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  35. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  36. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  37. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  39. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  40. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  41. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  44. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  45. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  46. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  47. 2026-08-26 08:43 UTCOSV refresh
  48. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  49. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  50. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  51. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  52. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  53. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  54. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  56. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  57. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  58. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  59. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  60. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  61. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  62. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  63. 2026-08-09 23:28 UTCEG score recompute
  64. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  65. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  66. 2026-08-08 06:15 UTCEG score recompute
  67. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  68. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  69. 2026-08-06 08:43 UTCEG score recompute
  70. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-66396?
CVE-2025-66396 is a high-severity vulnerability; its CVE record was published on December 17, 2025. ChurchCRM is an open-source church management system. Prior to version 6.5.3, a SQL injection vulnerability exists in the src/UserEditor.php file. When an administrator saves a user's configuration settings, the keys of the type POST parameter array are not properly sanitized or type-casted before…
When was the CVE record for CVE-2025-66396 published?
The CVE record for CVE-2025-66396 was published on December 17, 2025. 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 December 18, 2025; the record at its source may have been updated since.
Is CVE-2025-66396 actively exploited?
CVE-2025-66396 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-66396?
CVE-2025-66396 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2025-66396?
The CVE record for CVE-2025-66396 names the fix: "Version 6.5.3 patches the issue."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-66396

Explore →

Is Your Infrastructure Affected by CVE-2025-66396?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs