# CVE-2026-40593: ChurchCRM: Stored XSS in UserEditor.php via Login Name Field

> An administrator can inject malicious scripts via the username field, leading to stored XSS that executes in other administrators' browsers.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 18 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-7h46-9f64-p49q

## What is CVE-2026-40593?

CVE-2026-40593 is a medium-severity cross-site scripting vulnerability in ChurchCRM CRM, published on 18 Apr 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. In versions prior to 7.2.0, the User Editor (UserEditor.php) renders stored usernames directly into an HTML input value attribute without applying htmlspecialchars(). An administrator can save a username containing HTML attribute-breaking characters and event handlers, which execute in the browser of any administrator who subsequently views that user's editor page, 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-40593?


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

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

## Is CVE-2026-40593 being exploited?

There is no known exploitation of CVE-2026-40593 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40593 is a medium-severity cross-site scripting vulnerability in ChurchCRM CRM, published on 18 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-40593 in the wild and no public exploit code.

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-40593/ (Markdown: https://insights.sbomify.com/CVE-2026-40593/index.md)
```

## Sources

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

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