CVE-2026-35534 ChurchCRM has Stored XSS in PersonView.php via Facebook Field Attribute Injection
Authenticated users can inject JavaScript into the Facebook field, leading to session hijacking and account takeover for administrators 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-35534?
CVE-2026-35534 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 PersonView.php due to incorrect use of sanitizeText() as an output sanitizer for HTML attribute context. The function only strips HTML tags, it does not escape quote characters allowing an attacker to break out of the href attribute and inject arbitrary JavaScript event handlers. Any authenticated user with the EditRecords role can store the payload in a person's Facebook field. The XSS fires against any user who views that person's profile page, including administrators, enabling session hijacking and full account takeover. This vulnerability is fixed in 7.1.0.
Which versions are affected by CVE-2026-35534?
It affects 1 product.
Products include Churchcrm Churchcrm.
How do I fix CVE-2026-35534?
No fix has been published for CVE-2026-35534 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-35534 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35534 exists.
Other vulnerabilities in Churchcrm Churchcrm
Sources
Also known as GHSA-pqp6-54p2-m66f.