# CVE-2026-40483: ChurchCRM: Stored XSS in PledgeEditor.php via Donation Comment Field

> Authenticated users with Finance permissions can inject malicious scripts into donation comments, leading to stored XSS when viewed by others.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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:** 17 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-wjmf-w8gj-rx7g

## What is CVE-2026-40483?

CVE-2026-40483 is a medium-severity cross-site scripting vulnerability in ChurchCRM CRM, published on 17 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. In versions prior to 7.2.0, the Pledge Editor renders donation comment values directly into HTML input value attributes without escaping via htmlspecialchars(). An authenticated user with Finance permissions can inject HTML attribute-breaking characters and event handlers into the comment field, which are stored in the database and execute in the browser of any user who subsequently opens the pledge record for editing, resulting in stored XSS. This issue has been fixed in version 7.2.0.

Weakness: 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-40483?


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

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

## Is CVE-2026-40483 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40483 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40483 is a medium-severity cross-site scripting vulnerability in ChurchCRM CRM, published on 17 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-40483 exists.

Affected product: ChurchCRM CRM. 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-40483/ (Markdown: https://insights.sbomify.com/CVE-2026-40483/index.md)
```

## Sources

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

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