SQL ChurchCRM 5.5.0 POST Parameter EventEditor.php EID sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SQL ChurchCRM 5.5.0. It has been rated as critical. Affected is an unknown function of the file EventEditor.php of the component POST Parameter Handler. The manipulation of the argument EID leads to sql injection. This vulnerability is traded as CVE-2024-25896. There is no exploit available.
Details
A vulnerability was found in SQL ChurchCRM 5.5.0. It has been rated as critical. This issue affects an unknown function of the file EventEditor.php of the component POST Parameter Handler. The manipulation of the argument EID 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:
ChurchCRM 5.5.0 EventEditor.php is vulnerable to Blind SQL Injection (Time-based) via the EID POST parameter.
The weakness was shared 02/21/2024. The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-25896 since 02/12/2024. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
By approaching the search of inurl:EventEditor.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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
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.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/12/2024 🔍02/21/2024 🔍
02/21/2024 🔍
03/17/2025 🔍
Sources
Advisory: 6854Status: Not defined
CVE: CVE-2024-25896 (🔍)
GCVE (CVE): GCVE-0-2024-25896
GCVE (VulDB): GCVE-100-254429
Entry
Created: 02/21/2024 19:13Updated: 03/17/2025 20:43
Changes: 02/21/2024 19:13 (40), 03/13/2024 09:40 (1), 03/17/2025 20:43 (16)
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.