# CVE-2018-25393: Navigate CMS 2.8.5 Path Traversal via navigate_download.php

> Authenticated attackers can exploit path traversal in Navigate CMS to download arbitrary sensitive configuration and system files.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-rj56-vp9h-3frj

## What is CVE-2018-25393?

CVE-2018-25393 is a high-severity path traversal vulnerability in Navigatecms Navigate CMS, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Navigate CMS 2.8.5 contains a path traversal vulnerability that allows authenticated users to download arbitrary files by injecting directory traversal sequences in the id parameter. Attackers can send GET requests to navigate_download.php with path traversal payloads ../../../cfg/globals.php to access sensitive configuration files and system files outside the intended directory.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2018-25393?


## How do I fix CVE-2018-25393?

No fix has been published for CVE-2018-25393 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-25393 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25393 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25393 and fix it if it is affected.

What it is: CVE-2018-25393 is a high-severity path traversal vulnerability in Navigatecms Navigate CMS, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25393 exists.

Affected product: Navigatecms Navigate CMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-25393/ (Markdown: https://insights.sbomify.com/CVE-2018-25393/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-25393
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-25393
- OSV: https://osv.dev/vulnerability/CVE-2018-25393

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-25393/
Summaries are generated and may contain mistakes; the official description above is the record.