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

> An attacker can read arbitrary local files via path traversal in the filename parameter of catalog.php in PilusCart.

- **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:** 9 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h3cq-gj4m-j48p

## What is CVE-2019-16123?

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

### Official description

In Kartatopia PilusCart 1.4.1, the parameter filename in the file catalog.php is mishandled, leading to ../ Local File Disclosure.

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

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

It affects 1 product.


Products: Kartatopia Piluscart.

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

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

## Is CVE-2019-16123 being exploited?

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

Public exploit code:

- PilusCart <=1.4.1 - Local File Inclusion (nuclei): http/cves/2019/CVE-2019-16123.yaml

## Other vulnerabilities in n/a

- [CVE-2019-25672](https://insights.sbomify.com/CVE-2019-25672/): PilusCart 1.4.1 SQL Injection via send Parameter (high 8.8)
- [CVE-2019-9769](https://insights.sbomify.com/CVE-2019-9769/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16123 is a high-severity path traversal vulnerability in n/a, published on 9 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-16123 exists.

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-16123/ (Markdown: https://insights.sbomify.com/CVE-2019-16123/index.md)
```

## Sources

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

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