Syncplify Syncplify.me Server 5.0.37 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 Syncplify Syncplify.me Server 5.0.37. It has been rated as problematic. Affected by this issue is some unknown functionality. The manipulation leads to unquoted search path. This vulnerability is listed as CVE-2020-37230. The attack must be carried out locally. In addition, an exploit is available.
Details
A vulnerability was found in Syncplify Syncplify.me Server 5.0.37 and classified as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a unquoted search path vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Syncplify.me Server! 5.0.37 contains an unquoted service path vulnerability in the SMWebRestServicev5 service that allows local attackers to escalate privileges by exploiting the unquoted binary path. Attackers can insert a malicious executable into the service path and execute it with LocalSystem privileges when the service restarts or the system reboots.
The weakness was presented by Julio Aviña as 49009. It is possible to read the advisory at exploit-db.com. The identification of this vulnerability is CVE-2020-37230 since 05/15/2026. The exploitation is known 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 available 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.
Be aware that VulDB is the high quality source 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/15/2026 CVE reserved05/16/2026 Advisory disclosed
05/16/2026 VulDB entry created
05/16/2026 VulDB entry last update
Sources
Advisory: 49009Researcher: Julio Aviña
Status: Not defined
CVE: CVE-2020-37230 (🔒)
GCVE (CVE): GCVE-0-2020-37230
GCVE (VulDB): GCVE-100-364343
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/16/2026 18:04Changes: 05/16/2026 18:04 (78)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.