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

> Attackers can upload malicious files via the database restore feature to achieve remote code execution on the server.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-pqm7-g8px-9r77

## What is CVE-2025-68109?

CVE-2025-68109 is a critical vulnerability in Churchcrm Churchcrm, published on 17 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-552 (Files or Directories Accessible to External Parties), CWE-494 (Download of Code Without Integrity Check), CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-68109?

It affects 1 product.


Products: Churchcrm Churchcrm.

## How do I fix CVE-2025-68109?

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

## Is CVE-2025-68109 being exploited?

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

Public exploit code:

- ChurchCRM Database Restore RCE 6.2.0 (metasploit)

## Other vulnerabilities in Churchcrm Churchcrm

- [CVE-2026-39337](https://insights.sbomify.com/CVE-2026-39337/): ChurchCRM Affected by Unauthenticated RCE in Install Wizard (critical 10.0)
- [CVE-2025-62521](https://insights.sbomify.com/CVE-2025-62521/): ChurchCRM has unauthenticated RCE in its Install Wizard (critical 10.0)
- [CVE-2025-68110](https://insights.sbomify.com/CVE-2025-68110/): ChurchCRM discloses database information on error message (critical 10.0)
- [CVE-2024-53438](https://insights.sbomify.com/CVE-2024-53438/): SQL injection in n/a (critical 9.8)
- [CVE-2024-25894](https://insights.sbomify.com/CVE-2024-25894/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68109 and fix it if it is affected.

What it is: CVE-2025-68109 is a critical vulnerability in Churchcrm Churchcrm, published on 17 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68109 exists.

Affected product: Churchcrm Churchcrm. 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-2025-68109/ (Markdown: https://insights.sbomify.com/CVE-2025-68109/index.md)
```

## Sources

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

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