NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Plan (action score 40/100)

A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
Because a ready-made attack tool exists, priority is at least “Plan”.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.2 · v3.1—Weaponized No fix recorded

Published: Dec 17, 2025
Updated: Oct 1, 2026
EPSS: 1.5% · 75th percentile
CWE: CWE-78

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 28 / 40 · 7.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%
Ready-made attack tool: 12 / 40 · floor: at least 40

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.2
CNA · GitHub_M: 9.1; 1.9 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Weaponized exploit exists
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
churchcrm	churchcrm	cpe:2.3:a:churchcrm:churchcrm

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

churchcrm churchcrmbefore 6.5.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

ChurchCRM CRM
- < 6.5.3affected

Same product

churchcrm: all records

Other highest-scoring records for the same primary product.

CVE-2025-62521ChurchCRM has unauthenticated RCE in its Install Wizard
60This week
CVE-2026-39337ChurchCRM Affected by Unauthenticated RCE in Install Wizard
40Plan
CVE-2024-53438EventAttendance.php in ChurchCRM 5.7.0 is vulnerable to SQL injection.
39Monitor

Published before and after this one in the same product

← EarlierCVE-2025-68401Dec 17, 2025 · ChurchCRM has Stored Cross-Site Scripting (XSS) vulnerability that leads to session theft and account takeover
24Monitor
← EarlierCVE-2025-67875Dec 17, 2025 · ChurchCRM has stored XSS via Person Property Assignment Leading to Admin Session Hijacking
34Monitor
Later →CVE-2026-24854Jan 30, 2026 · Church CRM has SQL injection in PaddleNumEditor.php
35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

Metasploit module ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Metasploit module	exploit/multi/http/churchcrm_db_restore_rceChurchCRM Database Restore RCE 6.2.0exploit	2025-12-17

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

MetasploitDec 17, 2025-1 d
PublishedDec 17, 2025
TodayNov 11, 2026+328 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

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

nvd-primary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

All records