| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in ChurchCRM 4.5.3. The affected element is an unknown function of the file /churchcrm/EventAttendance.php. The manipulation of the argument Event leads to sql injection. This vulnerability is uniquely identified as CVE-2023-24787. Moreover, an exploit is present.
Details
A vulnerability was found in ChurchCRM 4.5.3. It has been rated as critical. This issue affects some unknown functionality of the file /churchcrm/EventAttendance.php. The manipulation of the argument Event with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
RESERVED churchcrm v4.5.3 was discovered to contain a SQL injection vulnerability via the Event parameter at /churchcrm/EventAttendance.php.
The weakness was disclosed 03/24/2023. The identification of this vulnerability is CVE-2023-24787 since 01/30/2023. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is available at packetstormsecurity.com. It is declared as proof-of-concept. By approaching the search of inurl:churchcrm/EventAttendance.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (51319). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.5
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/30/2023 🔍03/24/2023 🔍
03/24/2023 🔍
10/10/2024 🔍
Sources
Status: Not definedCVE: CVE-2023-24787 (🔍)
GCVE (CVE): GCVE-0-2023-24787
GCVE (VulDB): GCVE-100-223757
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/24/2023 06:50Updated: 10/10/2024 13:56
Changes: 03/24/2023 06:50 (37), 06/19/2024 03:06 (22), 10/10/2024 13:56 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.