# 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.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **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 available:** No
- **Published:** 7 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-pqp6-54p2-m66f

## 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.

Weakness: CWE-87 (Improper Neutralization of Alternate XSS Syntax), CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-35534?

It affects 1 product.


Products: 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.

## 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

- [CVE-2026-39337](https://insights.sbomify.com/CVE-2026-39337/): ChurchCRM Affected by Unauthenticated RCE in Install Wizard (critical 10.0)
- [CVE-2025-62521](https://insights.sbomify.com/CVE-2025-62521/): ChurchCRM has unauthenticated RCE in its Install Wizard (critical 10.0)
- [CVE-2025-68110](https://insights.sbomify.com/CVE-2025-68110/): ChurchCRM discloses database information on error message (critical 10.0)
- [CVE-2024-53438](https://insights.sbomify.com/CVE-2024-53438/): SQL injection in n/a (critical 9.8)
- [CVE-2024-25894](https://insights.sbomify.com/CVE-2024-25894/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35534 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35534 exists.

Affected product: Churchcrm Churchcrm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35534/ (Markdown: https://insights.sbomify.com/CVE-2026-35534/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35534
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35534
- OSV: https://osv.dev/vulnerability/CVE-2026-35534

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35534/
Summaries are generated and may contain mistakes; the official description above is the record.