ChurchCRM is an open-source church management system. Prior to version 7.4.0, Cross-Site Scripting (XSS) vulnerabilities were identified due to insufficient output encoding of user-controlled request parameter names and parameter values. The application reflects attacker-controlled input into JavaScript string contexts and HTML attribute contexts without proper sanitization or contextual output encoding. Affected endpoints observed during testing: /FamilyCustomFieldsEditor.php, /PaddleNumList.php and /admin/system/church-info. Potential consequences include session-token theft, account takeover, unauthorized actions on behalf of authenticated users, exposure of sensitive church member information, credential harvesting, phishing, and privilege escalation when administrators are targeted. This issue has been resolved in version 7.4.0.
CVE-2026-58411
This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% 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
- 7.0
- EG Score
- 7.0(medium)
- EPSS
- 26.9%
- KEV
- Not listed
Published
July 13, 2026
Last Modified
July 14, 2026
Advisory Details (1)
Auto-updated Jul 13, 2026Reflected Cross-Site Scripting (XSS) via unsanitized request parameter names and values · Advisory · ChurchCRM/CRM · GitHub
https://github.com/ChurchCRM/CRM/security/advisories/GHSA-p6j6-vrpg-4pp8Weakness 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-17 00:45 UTCEG score recompute
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 12:12 UTCEG score recompute
- 2026-07-15 23:39 UTCEG score recompute
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 11:05 UTCEG score recompute
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 22:30 UTCEG score recompute
- 2026-07-14 09:56 UTCEG score recompute
- 2026-07-13 21:23 UTCEG score recompute
- 2026-07-13 21:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-58411?
When was CVE-2026-58411 disclosed?
Is CVE-2026-58411 actively exploited?
What is the CVSS score of CVE-2026-58411?
How do I remediate CVE-2026-58411?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58411
Is Your Infrastructure Affected by CVE-2026-58411?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.