# CVE-2019-13063: Path traversal in n/a

> Attackers can exploit directory traversal in Sahi Pro to read arbitrary files and potentially execute code via remote file inclusion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q582-wgr3-m4j7

## What is CVE-2019-13063?

CVE-2019-13063 is a high-severity path traversal vulnerability in n/a, published on 23 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Within Sahi Pro 8.0.0, an attacker can send a specially crafted URL to include any victim files on the system via the script parameter on the Script_view page. This will result in file disclosure (i.e., being able to pull any file from the remote victim application). This can be used to steal and obtain sensitive config and other files. This can result in complete compromise of the application. The script parameter is vulnerable to directory traversal and both local and remote file inclusion.

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

## Which versions are affected by CVE-2019-13063?

It affects 1 product.


Products: Sahipro Sahi Pro.

## How do I fix CVE-2019-13063?

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

## Is CVE-2019-13063 being exploited?

There is no known exploitation of CVE-2019-13063 in the wild and no public exploit code.

Public exploit code:

- Sahi pro 8.x - Directory Traversal (exploitdb)
- Proof of concept tool to exploit the directory traversal and local file inclusion vulnerability that resides in the Sahi-pro web application CVE-2019-13063 (github_poc): https://github.com/0x6b7966/CVE-2019-13063-POC

## Other vulnerabilities in n/a

- [CVE-2019-15102](https://insights.sbomify.com/CVE-2019-15102/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-13597](https://insights.sbomify.com/CVE-2019-13597/): Command injection in n/a (critical 9.8)
- [CVE-2018-20469](https://insights.sbomify.com/CVE-2018-20469/): SQL injection in n/a (critical 9.8)
- [CVE-2018-20468](https://insights.sbomify.com/CVE-2018-20468/): Code injection in n/a (high 8.8)
- [CVE-2018-20470](https://insights.sbomify.com/CVE-2018-20470/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13063 and fix it if it is affected.

What it is: CVE-2019-13063 is a high-severity path traversal vulnerability in n/a, published on 23 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13063 in the wild and no public exploit code.

Affected product: n/a. 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-2019-13063/ (Markdown: https://insights.sbomify.com/CVE-2019-13063/index.md)
```

## Sources

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

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