CVE-2025-68109 affects ChurchCRM, an open-source church management system. In versions prior to 6.5.3, the Database Restore functionality does not properly validate uploaded file content or file extensions. This allows an attacker to upload a malicious server-side script such as a web shell, and then upload a .htaccess file to make that payload directly accessible and executable via the web server. Successful exploitation results in remote code execution on the underlying server. The issue is fixed in ChurchCRM 6.5.3.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution vulnerability in ChurchCRM referenced as a Metasploit module addition.
A critical remote code execution (RCE) vulnerability in ChurchCRM prior to version 6.5.3, due to improper validation of uploaded files in the Database Restore functionality, allowing attackers to upload and execute malicious web shells.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.