Seiko Epson Status Monitor 3 4_06 8.0 E_S60RPB.EXE unquoted search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Seiko Epson Status Monitor 3 4_06 8.0. This affects an unknown part of the file C:\Program Files\Common Files\EPSON\EPW!3SSRP\E_S60RPB.EXE. The manipulation results in unquoted search path. This vulnerability is reported as CVE-2020-36975. The attack requires a local approach. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, was found in Seiko Epson Status Monitor 3 4_06 8.0. Affected is an unknown functionality of the file C:\Program Files\Common Files\EPSON\EPW!3SSRP\E_S60RPB.EXE. 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. CVE summarizes:
EPSON Status Monitor 3 version 8.0 contains an unquoted service path vulnerability that allows local attackers to potentially execute arbitrary code by exploiting the service binary path. Attackers can leverage the unquoted path in 'C:\Program Files\Common Files\EPSON\EPW!3SSRP\E_S60RPB.EXE' to inject malicious executables and escalate privileges.
The weakness was disclosed by SamAlucard as 49141. The advisory is shared for download at exploit-db.com. This vulnerability is traded as CVE-2020-36975 since 01/27/2026. The exploitability is told to be difficult. The attack needs to be approached locally. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1574.009.
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 (49141). 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: 🔍
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
01/27/2026 Advisory disclosed01/27/2026 CVE reserved
01/27/2026 VulDB entry created
01/27/2026 VulDB entry last update
Sources
Advisory: 49141Researcher: SamAlucard
Status: Not defined
CVE: CVE-2020-36975 (🔒)
GCVE (CVE): GCVE-0-2020-36975
GCVE (VulDB): GCVE-100-343092
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/27/2026 20:52Changes: 01/27/2026 20:52 (80)
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.