CVE-2026-39328 ChurchCRM has Stored XSS in Social Profile Fields
Attackers can inject malicious scripts into profile fields to steal session cookies from other users, including administrators, when viewing the profile.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-39328?
CVE-2026-39328 is a high-severity cross-site scripting vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-39328?
It affects 1 product.
Products include Churchcrm Churchcrm.
How do I fix CVE-2026-39328?
No fix has been published for CVE-2026-39328 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-39328 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39328 exists.
Other vulnerabilities in Churchcrm Churchcrm
Sources
Also known as GHSA-fcp5-pwvj-v7xm.