Goal Reached Thanks to every supporter โ€” we hit 100%!

Goal: 1000 CNY ยท Raised: 1359 CNY

100%

CVE-2026-39337 โ€” AI Deep Analysis Summary

CVSS 10.0 ยท Critical

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: A code injection flaw in ChurchCRM's installation wizard. ๐Ÿ’ฅ **Consequences**: The `$dbPassword` variable is uncleaned, leading to **Pre-authentication Remote Code Execution (RCE)**.โ€ฆ

Q2Root Cause? (CWE/Flaw)

๐Ÿ›ก๏ธ **Root Cause**: **CWE-94** (Code Injection). ๐Ÿ› **Flaw**: The installation wizard fails to sanitize the `$dbPassword` input variable before execution.โ€ฆ

Q3Who is affected? (Versions/Components)

๐Ÿข **Vendor**: ChurchCRM. ๐Ÿ“ฆ **Product**: CRM System. ๐Ÿ“‰ **Affected Versions**: All versions **prior to 7.1.0**. If you are running v7.0.x or earlier, you are vulnerable.

Q4What can hackers do? (Privileges/Data)

๐Ÿ‘‘ **Privileges**: **Pre-authentication** access. No login needed! ๐Ÿ—„๏ธ **Data**: Full **Remote Code Execution**. Hackers can execute system commands, install backdoors, and take over the entire server infrastructure.

Q5Is exploitation threshold high? (Auth/Config)

๐Ÿ“‰ **Threshold**: **Extremely Low**. ๐Ÿšช **Auth**: **None required** (Pre-auth). ๐ŸŒ **Network**: Remote (AV:N). ๐ŸŽฏ **Complexity**: Low (AC:L). This is a critical, easy-to-exploit flaw.

Q6Is there a public Exp? (PoC/Wild Exploitation)

๐Ÿ“œ **Public Exp?**: **Yes**. A GitHub Security Advisory (GHSA-pm2v-ggh4-mp7p) has been published. While specific PoC code isn't listed in the snippet, the advisory confirms the vulnerability is known and exploitable.

Q7How to self-check? (Features/Scanning)

๐Ÿ” **Self-Check**: 1. Check your ChurchCRM version. 2. Look for the **Installation Wizard** endpoint. 3. Scan for unhandled `$dbPassword` parameters in POST requests during setup. 4.โ€ฆ

Q8Is it fixed officially? (Patch/Mitigation)

๐Ÿ”ง **Fix**: **Yes**. Upgrade to **ChurchCRM 7.1.0** or later. The vendor has acknowledged the issue via GitHub Security Advisory and released a patch to sanitize the input.

Q9What if no patch? (Workaround)

๐Ÿšง **Workaround**: If patching is impossible: 1. **Block** access to the installation wizard from the internet. 2. Ensure the installation wizard is **disabled** or removed in production. 3.โ€ฆ

Q10Is it urgent? (Priority Suggestion)

๐Ÿ”ฅ **Urgency**: **CRITICAL**. ๐Ÿšจ **Priority**: **Immediate Action Required**. With **CVSS 9.8** (High) and **Pre-auth RCE**, this is a top-priority vulnerability. Patch immediately to prevent total server compromise.