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.
CVE-2026-58409
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 63% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EPSS
- 36.7%
- KEV
- Not listed
Published
July 13, 2026
Last Modified
July 14, 2026
Advisory Details (1)
Auto-updated Jul 13, 2026Authenticated Remote Code Execution (RCE) via Malicious Plugin Upload in ChurchCRM · Advisory · ChurchCRM/CRM · GitHub
https://github.com/ChurchCRM/CRM/security/advisories/GHSA-37mf-vq43-5qp9Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-15 10:57 UTCEG score recompute
- 2026-07-15 06:42 UTCEG score recompute
- 2026-07-15 02:25 UTCEG score recompute
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 22:11 UTCEG score recompute
- 2026-07-14 17:55 UTCEG score recompute
- 2026-07-14 13:39 UTCEG score recompute
- 2026-07-14 09:24 UTCEG score recompute
- 2026-07-14 05:08 UTCEG score recompute
- 2026-07-14 00:52 UTCEG score recompute
- 2026-07-13 20:38 UTCEG score recompute
- 2026-07-13 20:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-434
Frequently asked(5)
What is CVE-2026-58409?
When was CVE-2026-58409 disclosed?
Is CVE-2026-58409 actively exploited?
What is the CVSS score of CVE-2026-58409?
How do I remediate CVE-2026-58409?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58409
Is Your Infrastructure Affected by CVE-2026-58409?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.