| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Dokmee ECM 7.4.6. It has been classified as critical. Impacted is an unknown function of the file GettingStarted/SaveSQLConnectionAsync /#/gettingstarted. The manipulation leads to an unknown weakness. This vulnerability is traded as CVE-2023-47261. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Dokmee ECM 7.4.6 and classified as critical. This issue affects an unknown code block of the file GettingStarted/SaveSQLConnectionAsync /#/gettingstarted. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Dokmee ECM 7.4.6 allows remote code execution because the response to a GettingStarted/SaveSQLConnectionAsync /#/gettingstarted request contains a connection string for privileged SQL Server database access, and xp_cmdshell can be enabled.
The weakness was shared 12/14/2023. It is possible to read the advisory at h3x0s3.github.io. The identification of this vulnerability is CVE-2023-47261 since 11/05/2023. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 8.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: Privilege escalationCWE: Unknown
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/05/2023 🔍12/14/2023 🔍
12/14/2023 🔍
01/11/2024 🔍
Sources
Advisory: h3x0s3.github.ioStatus: Not defined
CVE: CVE-2023-47261 (🔍)
GCVE (CVE): GCVE-0-2023-47261
GCVE (VulDB): GCVE-100-248099
Entry
Created: 12/14/2023 18:43Updated: 01/11/2024 09:19
Changes: 12/14/2023 18:43 (36), 01/11/2024 09:19 (11)
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.