# CVE-2026-40581: ChurchCRM: Cross-Site Request Forgery (CSRF) in SelectDelete.php Leading to Permanent Data Deletion

> An attacker can trick an authenticated administrator into permanently deleting family records via a crafted GET request in ChurchCRM.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-6qxv-xw9j-77pj

## What is CVE-2026-40581?

CVE-2026-40581 is a high-severity vulnerability in ChurchCRM CRM, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, 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 family record deletion endpoint (SelectDelete.php) performs permanent, irreversible deletion of family records and all associated data via a plain GET request with no CSRF token validation. An attacker can craft a malicious page that, when visited by an authenticated administrator, silently triggers deletion of targeted family records including associated notes, pledges, persons, and property data without any user interaction. This issue has been fixed in version 7.2.0.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-40581 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40581 is a high-severity vulnerability in ChurchCRM CRM, published on 17 Apr 2026. An attacker can exploit it over the internet without logging in, 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-40581 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-40581/ (Markdown: https://insights.sbomify.com/CVE-2026-40581/index.md)
```

## Sources

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

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