# GHSA-8h8v-6qqm-fwpq: Path Traversal in express-cart

> An attacker can exploit a path traversal vulnerability in the express-cart library to read arbitrary files from the server.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 1 Sep 2020

## What is GHSA-8h8v-6qqm-fwpq?

GHSA-8h8v-6qqm-fwpq is a path traversal vulnerability in express-cart, published on 1 Sep 2020. It can be exploited over the network.

### Official description

Versions of `express-cart` before 1.1.7 are vulnerable to Path Traversal.

## Recommendation

Update to version 1.1.7 or later.

## Which versions are affected by GHSA-8h8v-6qqm-fwpq?

2 open source packages ship an affected version, including express-cart.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `express-cart` | npm | All versions | 1.1.7 |
| `express-cart` | npm | All versions | 1.1.7 |

## How do I fix GHSA-8h8v-6qqm-fwpq?

Upgrade express-cart to 1.1.7 or later.

## Is GHSA-8h8v-6qqm-fwpq being exploited?

There is no known exploitation of GHSA-8h8v-6qqm-fwpq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8h8v-6qqm-fwpq and fix it if it is affected.

What it is: GHSA-8h8v-6qqm-fwpq is a path traversal vulnerability in express-cart, published on 1 Sep 2020. It can be exploited over the network.
Exploitation: There is no known exploitation of GHSA-8h8v-6qqm-fwpq in the wild and no public exploit code.

Affected packages and fixed versions:
- express-cart (npm): affected all versions; fixed in 1.1.7
- express-cart (npm): affected all versions; fixed in 1.1.7

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/GHSA-8h8v-6qqm-fwpq/ (Markdown: https://insights.sbomify.com/GHSA-8h8v-6qqm-fwpq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8h8v-6qqm-fwpq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8h8v-6qqm-fwpq/
Summaries are generated and may contain mistakes; the official description above is the record.