LiteManager Mikogo 5.2.2.150317 Service Windows Service unquoted search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in LiteManager Mikogo 5.2.2.150317. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Service Windows Service. Performing a manipulation results in unquoted search path. This vulnerability is known as CVE-2019-25308. Attacking locally is a requirement. Furthermore, an exploit is available.
Details
A vulnerability classified as critical has been found in LiteManager Mikogo 5.2.2.150317. This affects an unknown function of the component Service Windows Service. The manipulation with an unknown input leads to a unquoted search path vulnerability. CWE is classifying the issue as CWE-428. The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Mikogo 5.2.2.150317 contains an unquoted service path vulnerability in the Mikogo-Service Windows service configuration. Attackers can exploit the unquoted path to inject and execute malicious code with LocalSystem privileges by placing executable files in specific path locations.
The weakness was published by Cakes as 47510. It is possible to read the advisory at exploit-db.com. This vulnerability is uniquely identified as CVE-2019-25308 since 02/10/2026. The exploitability is told to be difficult. Attacking locally is a requirement. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1574.009 according to MITRE ATT&CK.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
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 (47510). 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: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.0
VulDB Temp Score: 6.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (VulnCheck): 🔒
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: Unquoted search pathCWE: CWE-428 / CWE-426
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
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
02/10/2026 CVE reserved02/11/2026 Advisory disclosed
02/11/2026 VulDB entry created
02/27/2026 VulDB entry last update
Sources
Advisory: 47510Researcher: Cakes
Status: Not defined
CVE: CVE-2019-25308 (🔒)
GCVE (CVE): GCVE-0-2019-25308
GCVE (VulDB): GCVE-100-345555
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/11/2026 16:54Updated: 02/27/2026 02:11
Changes: 02/11/2026 16:54 (80), 02/27/2026 02:11 (1)
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.