CVE-2026-58409

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
9.1EG
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.8%CVSS: 9.1Exploit: 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 7.4.0, an authenticated administrator can achieve Remote Code Execution (RCE) on the server by installing a malicious plugin ZIP archive containing a PHP webshell. The application explicitly includes 'php' in its ALLOWED_EXTENSIONS list, while the dangerous extensions denylist (DENIED_EXTENSIONS) fails to block standard .php files. Because php is explicitly included in the allowed extension list for plugin archives, and extracted files are placed directly under the web root, any PHP file inside the ZIP becomes immediately executable via HTTP — without even needing to "enable" the plugin through the application UI. The /plugins/install-url API route (management.php) allows an administrator to source the malicious ZIP from any attacker-controlled HTTPS URL, validating it only against an attacker-supplied SHA-256 hash. This issue has been fixed in version 7.4.0.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
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.8%
EPSS %ILE
54th
KEV
Not listed

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.

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 13, 2026

Last Modified

July 14, 2026

Advisory Details (1)

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

Authenticated Remote Code Execution (RCE) via Malicious Plugin Upload in ChurchCRM · Advisory · ChurchCRM/CRM · GitHub

https://github.com/ChurchCRM/CRM/security/advisories/GHSA-37mf-vq43-5qp9

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 36× 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 100 of 143 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. None are among the latest 100 rows. The 43 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58409?
CVE-2026-58409 is a critical-severity vulnerability; its CVE record was published on July 13, 2026. ChurchCRM is an open-source church management system. Prior to version 7.4.0, an authenticated administrator can achieve Remote Code Execution (RCE) on the server by installing a malicious plugin ZIP archive containing a PHP webshell. The application explicitly includes 'php' in its…
When was the CVE record for CVE-2026-58409 published?
The CVE record for CVE-2026-58409 was published on July 13, 2026. 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 July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-58409 actively exploited?
CVE-2026-58409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58409?
CVE-2026-58409 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58409?
The CVE record for CVE-2026-58409 names the fix: "This issue has been fixed in version 7.4.0."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58409

Explore →

Is Your Infrastructure Affected by CVE-2026-58409?

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

Book a Demo →Browse All CVEs