# CVE-2026-44548: ChurchCRM: CSRF via legacy GET-delete pages (FundRaiserDelete.php, PropertyTypeDelete.php, NoteDelete.php)


- **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
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 13 May 2026

## What is CVE-2026-44548?

CVE-2026-44548 is a high-severity vulnerability in ChurchCRM CRM, published on 12 May 2026. 

### Official description

ChurchCRM is an open-source church management system. Prior to 7.3.2, top-level cross-site GET navigation from an attacker-controlled page to FundRaiserDelete.php, PropertyTypeDelete.php, or NoteDelete.php causes a logged-in ChurchCRM user with the relevant role to silently delete records, including cascaded property and record-to-property assignments. This vulnerability is fixed in 7.3.2.

Weakness: CWE-650 (Trusting HTTP Permission Methods on the Server Side), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-44548 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44548 is a high-severity vulnerability in ChurchCRM CRM, published on 12 May 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44548 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-44548/ (Markdown: https://insights.sbomify.com/CVE-2026-44548/index.md)
```

## Sources

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

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