# CVE-2018-3727: Path Traversal in 626

> A path traversal vulnerability in the 626 Node.js module allows attackers to read arbitrary files from the server filesystem.

- **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:** 7 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r4r9-mgjc-g6q3

## What is CVE-2018-3727?

CVE-2018-3727 is a high-severity path traversal vulnerability in HackerOne 626 node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

626 node module suffers from a Path Traversal vulnerability due to lack of validation of file, which allows a malicious user to read content of any file with known path.

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

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

2 open source packages ship an affected version, including 626. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `626` | npm | From 0.0.0 | None |
| `626` | npm | From 0.0.0 | None |

Products: 626 Project 626.

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

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

## Is CVE-2018-3727 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3727 is a high-severity path traversal vulnerability in HackerOne 626 node module, published on 7 Jun 2018. 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-2018-3727 in the wild and no public exploit code.

Affected packages and fixed versions:
- 626 (npm): affected from 0.0.0; no fix listed
- 626 (npm): affected from 0.0.0; no fix listed

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

## Sources

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

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