Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/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-2025-61666 is a high-severity Path Traversal (CWE-22) vulnerability in Projectblack (inferred from references). Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique /etc/passwd and /etc/shadow (T1003.008); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — 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.
Traccar, an open source GPS tracking system, contains a path traversal vulnerability (CWE-22) that enables unauthenticated local file inclusion. Default installations on Windows in versions 6.1 through 6.8.1 are affected because the web override feature is enabled by default, while versions 5.8 through 6.0 are affected only when the configuration explicitly sets <entry key='web.override'>./override</entry>. The flaw resides in DefaultOverrideServlet and permits reading arbitrary files on the filesystem, including the Traccar configuration file that may contain passwords.
An unauthenticated remote attacker can supply crafted paths to the override servlet and retrieve sensitive files without authentication or user interaction. Successful exploitation yields disclosure of configuration secrets or other filesystem contents but does not permit modification or service disruption. The CVSS 4.0 score of 8.7 reflects the network-accessible, low-complexity nature of the attack.
The official advisory GHSA-hprc-rph8-fj87 and the Traccar 6.9.0 release remove the vulnerable servlet code entirely. Administrators are advised to upgrade to 6.9.0 or later; non-default installations should also verify that the web.override setting is absent or disabled. The associated EPSS score rose from a low baseline to a peak of 0.0324, indicating increased exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-33211
Vulnerability Data
Traccar is an open source GPS tracking system. Default installs of Traccar on Windows between versions 6.1- 6.8.1 and non default installs between versions 5.8 - 6.0 are vulnerable to unauthenticated local file inclusion attacks which can lead to leakage…
more
of passwords or any file on the file system including the Traccar configuration file. Versions 5.8 - 6.0 are only vulnerable if <entry key='web.override'>./override</entry> is set in the configuration file. Versions 6.1 - 6.8.1 are vulnerable by default as the web override is enabled by default. The vulnerable code is removed in version 6.9.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
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.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
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 catches path traversal via static/dynamic analysis.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.