MiniTool Power Data Recovery up to 11.5 In-app Payment System channel accessible
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MiniTool Power Data Recovery up to 11.5 and classified as problematic. Affected is an unknown function of the component In-app Payment System. The manipulation results in channel accessible. This vulnerability is cataloged as CVE-2023-38353. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in MiniTool Power Data Recovery up to 11.5. It has been classified as problematic. Affected is an unknown code of the component In-app Payment System. The manipulation with an unknown input leads to a channel accessible vulnerability. CWE is classifying the issue as CWE-300. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. This is going to have an impact on confidentiality. CVE summarizes:
MiniTool Power Data Recovery 11.5 contains an insecure in-app payment system that allows attackers to steal highly sensitive information through a man in the middle attack.
The weakness was shared 09/19/2023. The advisory is shared for download at 0dr3f.github.io. This vulnerability is traded as CVE-2023-38353 since 07/15/2023. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 01/19/2026). The MITRE ATT&CK project declares the attack technique as T1557.
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 EUVD (EUVD-2023-42170). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
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: Channel accessibleCWE: CWE-300
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
07/15/2023 🔍09/19/2023 🔍
09/19/2023 🔍
01/19/2026 🔍
Sources
Advisory: 0dr3f.github.ioStatus: Not defined
CVE: CVE-2023-38353 (🔍)
GCVE (CVE): GCVE-0-2023-38353
GCVE (VulDB): GCVE-100-239964
EUVD: 🔍
Entry
Created: 09/19/2023 19:07Updated: 01/19/2026 05:43
Changes: 09/19/2023 19:07 (38), 10/13/2023 08:36 (11), 01/19/2026 05:43 (16)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.