dbcve.org
Navbox FirmwareOperating system · Navtor

CVE-2026-2753

HIGH · 7.5 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 4.14.1.2 or later.
See remediation →
84/100
Remediation priority · High
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
An Absolute Path Traversal vulnerability exists in Navtor NavBox. The application exposes an HTTP service that fails to properly sanitize user-supplied path input. Unauthenticated remote attackers can exploit this issue by submitting requests containing absolute filesystem paths. Successful exploitation allows the attacker to retrieve arbitrary files from the underlying filesystem, limited only by the privileges of the service process. This can lead to the exposure of sensitive configuration files and system information.

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 · moderate confidence

Absolute path traversal vulnerability in Navtor NavBox's HTTP service. The application fails to sanitize user-supplied path inputs, allowing unauthenticated remote attackers to submit requests containing absolute filesystem paths. Successful exploitation enables retrieval of arbitrary files from the underlying filesystem, limited only by the service process privileges, exposing sensitive configuration files and system information.

MitigationImplement strict input validation to reject absolute paths and enforce path normalization with allow-listing of permitted directories; also restrict service account filesystem privileges to minimize exposure.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Navbox FirmwareOperating system
Affected:>= 4.12.0.3, < 4.14.1.2

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 NavBox firmware version
    Access the NavBox administrative interface or check the device/system information panel to retrieve the installed firmware version number.
    Affected if The installed firmware version is >= 4.12.0.3 and < 4.14.1.2, placing it within the affected range.
  2. Locate the HTTP service endpoint
    Identify the URL or network address used to access the NavBox HTTP web interface. This is typically the IP or hostname of the NavBox device on ports 80 or 443.
    Affected if The HTTP service is accessible over the network, exposing the web interface to requests.
  3. Verify the HTTP service processes path inputs
    Submit a test request to the HTTP service with a path parameter. Inspect whether the application accepts and processes absolute filesystem paths (e.g., /etc/, C:\, or similar full paths) as input.
    Affected if The service accepts and resolves absolute path inputs without rejecting them, indicating the vulnerability is present.
  4. Confirm file access via path traversal
    Attempt to retrieve a known file using an absolute path through the HTTP interface. Compare the response to verify if arbitrary file disclosure is possible.
    Affected if The service returns file contents when absolute paths are supplied, demonstrating the path traversal flaw is exploitable.

The environment is affected if the installed NavBox firmware version falls within 4.12.0.3 to 4.14.1.2 and the HTTP service accepts and processes absolute filesystem path inputs, allowing unauthorized file retrieval.

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
Upgrade available Upgrade to 4.14.1.2 or later
Fixed in 4.14.1.2
Interim mitigation

Implement strict input validation to reject absolute paths and enforce path normalization with allow-listing of permitted directories; also restrict service account filesystem privileges to minimize exposure.

Recommended fix Moderate confidence

Navbox Firmware 4.14.1.2 or later

  1. Identify the current firmware version of the NavBox device
  2. Download Navbox Firmware version 4.14.1.2 or later from the official vendor (Navtor)
  3. Follow the vendor's standard firmware upgrade procedure for NavBox devices
  4. After upgrade, verify the device is running version 4.14.1.2 or higher
  5. Test that the path traversal vulnerability is no longer exploitable

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

Fix this in Navbox Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2753 — 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-2026-2753 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