dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-44548

HIGH · 8.1 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a CSRF (Cross-Site Request Forgery) vulnerability in ChurchCRM where attacker-controlled pages can trigger silent record deletion via GET requests to FundRaiserDelete.php, PropertyTypeDelete.php, and NoteDelete.php. A logged-in user with the relevant role visiting a malicious site will unknowingly trigger deletion of records including cascaded property and record-to-property assignments.

MitigationUpgrade to ChurchCRM version 7.3.2 or later, which implements CSRF token validation on the delete endpoints to prevent unauthenticated cross-site deletion requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate ChurchCRM installation
    Search for ChurchCRM files on the server, typically in web root directories. Look for the presence of ChurchCRM configuration files or the main index.php
    Affected if ChurchCRM is not found on the system, the system is not affected by this CVE
  2. Determine installed ChurchCRM version
    Check the version file or header files in the ChurchCRM installation. Common locations include version.php, includes/config.php, or a VERSION file in the root directory
    Affected if The installed version is earlier than 7.3.2 (e.g., 7.3.1, 7.3.0, earlier releases)
  3. Verify affected delete endpoints exist
    Locate and confirm the presence of FundRaiserDelete.php, PropertyTypeDelete.php, and NoteDelete.php in the ChurchCRM web directory, typically under the root or a module subdirectory
    Affected if Any of these three PHP files exist in the installation and the version is below 7.3.2
  4. Inspect delete endpoints for CSRF protection
    Open each affected PHP file (FundRaiserDelete.php, PropertyTypeDelete.php, NoteDelete.php) and search for CSRF token validation logic, such as checks for token presence, session validation, or request verification before performing delete operations
    Affected if The delete endpoints lack CSRF token validation and allow deletion via GET requests without verifying the request origin

A ChurchCRM installation is affected if it is running a version earlier than 7.3.2 and contains the vulnerable delete endpoints without CSRF token validation logic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to ChurchCRM version 7.3.2 or later, which implements CSRF token validation on the delete endpoints to prevent unauthenticated cross-site deletion requests.

Recommended fix High confidence

ChurchCRM 7.3.2

  1. Backup your ChurchCRM database and files before upgrading
  2. Download ChurchCRM version 7.3.2 from the official GitHub repository (github.com/ChurchCRM/CRM)
  3. Extract and install the new version, replacing the previous installation
  4. Verify that the following files now include CSRF protection: FundRaiserDelete.php, PropertyTypeDelete.php, NoteDelete.php
  5. Test that the delete operations require POST requests with valid anti-CSRF tokens
  6. Confirm the application functions normally after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44548 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44548 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data