# CVE-2026-32880: ChurchCRM is vulnerable to Stored XSS through JSON handling in SystemSettings.php

> An admin can inject JavaScript via JSON settings, leading to stored XSS when other admins view the settings page.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-7gq6-xmpx-qc7c

## What is CVE-2026-32880?

CVE-2026-32880 is a medium-severity cross-site scripting vulnerability in Churchcrm Churchcrm, published on 20 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

ChurchCRM is an open-source church management system. Versions prior to 7.0.2 allow an admin user to edit JSON type system settings to store a JavaScript payload that can execute when any admin views the system settings. The JSON input is left unescaped/unsanitized in SystemSettings.php, leading to XSS. This issue has been fixed in version 7.0.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Churchcrm Churchcrm.

## How do I fix CVE-2026-32880?

No fix has been published for CVE-2026-32880 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32880 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32880 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-32880 and fix it if it is affected.

What it is: CVE-2026-32880 is a medium-severity cross-site scripting vulnerability in Churchcrm Churchcrm, published on 20 Mar 2026. An attacker needs administrator access to exploit it, 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-32880 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-32880/ (Markdown: https://insights.sbomify.com/CVE-2026-32880/index.md)
```

## Sources

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

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