CVE-2019-25275
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2019-25275 is a high-severity Unquoted Search Path or Element (CWE-428) vulnerability in Filehorse (inferred from references). Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2019-25275 is an unquoted service path vulnerability in BartVPN version 1.2.2, specifically affecting the BartVPNService component. This issue, mapped to CWE-428, arises from an unquoted binary path in the service configuration, enabling local attackers to potentially execute arbitrary code with elevated system privileges. Attackers exploit it by placing malicious executables in specific file system locations that the Windows service manager searches prior to the legitimate path, thereby hijacking the service's execution context. The vulnerability carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and was published on 2026-02-05.
A local attacker with low privileges (PR:L) can exploit this vulnerability with low complexity (AC:L) and no user interaction (UI:N). Upon successful exploitation, the attacker gains the ability to execute arbitrary code under the elevated privileges of the BartVPNService, typically SYSTEM level, resulting in high impacts to confidentiality, integrity, and availability (C:H/I:H/A:H). This could lead to full system compromise on affected Windows hosts running the vulnerable BartVPN installation.
Advisories and references, including an exploit demonstration at https://www.exploit-db.com/exploits/47675 and a detailed write-up from Vulncheck at https://www.vulncheck.com/advisories/bartvpn-bartvpnservice-unquoted-service-path, provide technical details on the flaw and exploitation methods. Additional context appears at https://www.filehorse.com/. Practitioners should consult these for vendor-specific guidance on patches or workarounds, as no mitigation details are specified in the core CVE data.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2019-19392
Vulnerability Data
BartVPN 1.2.2 contains an unquoted service path vulnerability in the BartVPNService that allows local attackers to potentially execute arbitrary code with elevated system privileges. Attackers can exploit the unquoted binary path by placing malicious executables in specific file system locations…
more
to hijack the service's execution context.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover unquoted search paths through static analysis or dynamic test cases.
Documented development standards and tools can mandate proper quoting and escaping of path elements.
Engineering principles can require safe construction and quoting of search paths and command elements.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent path-handling flaws such as unquoted elements during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect unquoted search-path issues before deployment.
Enforcing controlled software installation can prevent unquoted search-path elements in executables and scripts.
Secure development lifecycle practices include input validation and path handling that reduce unquoted search-path weaknesses.
Secure system architecture and engineering principles require safe path construction and quoting conventions.
Secure coding standards directly mandate quoting search paths and avoiding unsafe path construction.
Change-management processes can enforce review of path-handling changes that might introduce unquoted elements.