3CX prior 18.0.9.23/20.0.0.1494 first name/search string/email address sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in 3CX. This affects an unknown part. The manipulation of the argument first name/search string/email address leads to sql injection. This vulnerability is uniquely identified as CVE-2023-49954. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in 3CX. This issue affects an unknown code. The manipulation of the argument first name/search string/email address 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:
The CRM Integration in 3CX before 18.0.9.23 and 20 before 20.0.0.1494 allows SQL Injection via a first name, search string, or email address.
The weakness was disclosed 12/25/2023. It is possible to read the advisory at cve-2023-49954.github.io. The identification of this vulnerability is CVE-2023-49954 since 12/03/2023. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
Upgrading to version 18.0.9.23 or 20.0.0.1494 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-53849). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: 3CX 18.0.9.23/20.0.0.1494
Timeline
12/03/2023 🔍12/25/2023 🔍
12/25/2023 🔍
03/05/2026 🔍
Sources
Advisory: cve-2023-49954.github.ioStatus: Confirmed
CVE: CVE-2023-49954 (🔍)
GCVE (CVE): GCVE-0-2023-49954
GCVE (VulDB): GCVE-100-248987
EUVD: 🔍
Entry
Created: 12/25/2023 10:28Updated: 03/05/2026 12:45
Changes: 12/25/2023 10:28 (38), 01/19/2024 08:18 (11), 03/05/2026 12:45 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.