CVE-2026-39328
Stored XSS in ChurchCRM profile fields; cookie theft on profile view; fixed in 7.1.0.
Is CVE-2026-39328 being exploited?
Not confirmed. CVE-2026-39328 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-39328?
CVE-2026-39328 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-39328?
Yes. A fix has been recorded for CVE-2026-39328. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-39328 affect?
CVE-2026-39328 affects ChurchCRM (<7.1.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-39328?
Patch to 7.1.0+; rotate sessions; verify cookies
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Non-admins with EditSelf can inject JS; viewing attacker’s profile triggers cookie exfiltration, risking session hijack.
Immediate action required
- affected< 7.1.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.