| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SOUND4 Server Service 4.1.102. It has been rated as problematic. This vulnerability affects unknown code. This manipulation causes unquoted search path. This vulnerability appears as CVE-2023-53965. The attack requires local access. In addition, an exploit is available.
Details
A vulnerability was found in SOUND4 Server Service 4.1.102. It has been declared as critical. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a unquoted search path vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
SOUND4 Server Service 4.1.102 contains an unquoted service path vulnerability that allows local non-privileged users to potentially execute code with elevated system privileges. Attackers can exploit the unquoted binary path by inserting malicious code in the system root path that could execute with LocalSystem privileges during service startup.
The weakness was presented by Gjoko Krstic as 51167. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2023-53965 since 12/19/2025. The exploitation appears to be difficult. An attack has to be approached locally. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1574.009 for this issue.
It is possible to download the exploit 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 databases at Exploit-DB (51167) and EUVD (EUVD-2023-60227). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.7VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.0
VulDB Temp Score: 6.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
CNA Base Score: 8.4
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
12/19/2025 CVE reserved12/22/2025 Advisory disclosed
12/22/2025 VulDB entry created
01/29/2026 VulDB entry last update
Sources
Advisory: 51167Researcher: Gjoko Krstic
Status: Not defined
CVE: CVE-2023-53965 (🔒)
GCVE (CVE): GCVE-0-2023-53965
GCVE (VulDB): GCVE-100-337813
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/22/2025 23:50Updated: 01/29/2026 17:25
Changes: 12/22/2025 23:50 (79), 12/23/2025 00:17 (1), 01/29/2026 17:25 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.