dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-61666

HIGH · 8.7 CVSS v4.0 Published 2025-10-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated local file inclusion vulnerability in Traccar GPS tracking system on Windows allows attackers to read arbitrary files including configuration files containing passwords. Versions 6.1-6.8.1 are vulnerable by default due to the web.override setting being enabled, while versions 5.8-6.0 are only vulnerable when this setting is manually configured.

MitigationUpgrade to Traccar version 6.9.0 or later which removes the vulnerable code, or disable the web.override setting in the configuration file if upgrading is not immediately possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Traccar version
    Locate the Traccar installation directory on Windows, then check the version information - typically found in a version file, README, or the main traccar.jar/Traccar.exe file properties. Alternatively, check the startup logs which often display the version on launch.
    Affected if The installed version falls between 5.8 and 6.8.1 inclusive.
  2. Locate traccar.xml configuration
    Find the traccar.xml configuration file in the Traccar installation directory or in a standard configuration folder (commonly under the installation root or a config subdirectory).
    Affected if The file exists and contains a web.override configuration entry.
  3. Inspect web.override setting
    Open traccar.xml in a text editor and search for the 'web.override' element. Note its value and whether it appears with a specific configuration value or is just present as an empty element.
    Affected if For versions 6.1-6.8.1: web.override is present in the configuration. For versions 5.8-6.0: web.override is explicitly set to a value (not just present as an empty element).
  4. Verify the override parameter is accessible
    Test if the LFI is exploitable by attempting to access a known file via the web.override parameter in the Traccar web interface URL (for example, by making a request to an endpoint that processes the web.override parameter to include files).
    Affected if The web server responds with contents of arbitrary files when the web.override parameter is manipulated.

You are affected if your Traccar version is 6.1-6.8.1 with web.override present in traccar.xml, or version 5.8-6.0 with web.override explicitly configured, allowing unauthenticated file reads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Traccar version 6.9.0 or later which removes the vulnerable code, or disable the web.override setting in the configuration file if upgrading is not immediately possible.

Recommended fix High confidence

6.9.0 or later

  1. 1. Identify the current Traccar version by checking the installed application or configuration files
  2. 2. Back up the existing Traccar installation, including the configuration file (usually traccar.xml) and any database
  3. 3. Stop the Traccar service to prevent data loss during the upgrade
  4. 4. Download Traccar version 6.9.0 or later from the official GitHub repository (github.com/traccar)
  5. 5. Install the new version following the standard installation process for your Windows environment
  6. 6. Restore the backed-up configuration file to the new installation
  7. 7. Start the Traccar service and verify the application is running correctly
  8. 8. Test that the path traversal vulnerability is no longer exploitable by attempting to access a known file via the web interface
Caveat Review the release notes between your current version and 6.9.0 for any breaking changes in configuration or functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61666 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61666 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data