# CVE-2023-37474: Path traversal in copyparty

> An attacker can access files outside the web root via path traversal in the .cpr subfolder of the copyparty file server.

- **Severity:** High 7.5 (`CVSS:3.0/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:** Yes
- **Published:** 14 Jul 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-pxfv-7rr3-2qjg, PYSEC-2023-127

## What is CVE-2023-37474?

CVE-2023-37474 is a high-severity path traversal vulnerability in 9001 copyparty, published on 14 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Copyparty is a portable file server. Versions prior to 1.8.2 are subject to a path traversal vulnerability detected in the `.cpr` subfolder. The Path Traversal attack technique allows an attacker access to files, directories, and commands that reside outside the web document root directory. This issue has been addressed in commit `043e3c7d` which has been included in release 1.8.2. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

## Which versions are affected by CVE-2023-37474?

3 open source packages ship an affected version, including copyparty. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `copyparty` | PyPI | All versions | 1.8.2 |
| `copyparty` | PyPI | All versions | 1.8.2 |
| `copyparty` | PyPI | All versions | 1.8.2 |

Products: 9001 Copyparty.

## How do I fix CVE-2023-37474?

Upgrade copyparty to 1.8.2 or later.

## Is CVE-2023-37474 being exploited?

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

Public exploit code:

- https://github.com/ilqarli27/CVE-2023-37474 (github_poc): https://github.com/ilqarli27/CVE-2023-37474
- Copyparty <= 1.8.2 - Directory Traversal (nuclei): http/cves/2023/CVE-2023-37474.yaml

## Other vulnerabilities in 9001 copyparty

- [CVE-2023-41471](https://insights.sbomify.com/CVE-2023-41471/): Cross-site scripting in n/a (high 7.8)
- [CVE-2025-54796](https://insights.sbomify.com/CVE-2025-54796/): Copyparty is vulnerable to Regex Denial of Service (ReDoS) attacks through "Recent Uploads" page (high 7.5)
- [CVE-2025-54589](https://insights.sbomify.com/CVE-2025-54589/): copyparty Reflected XSS via Filter Parameter (medium 6.3)
- [CVE-2023-38501](https://insights.sbomify.com/CVE-2023-38501/): copyparty vulnerable to reflected cross-site scripting via k304 parameter (medium 6.3)
- [CVE-2026-27948](https://insights.sbomify.com/CVE-2026-27948/): Copyparty vulnerable to eflected cross-site scripting via setck parameter (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37474 and fix it if it is affected.

What it is: CVE-2023-37474 is a high-severity path traversal vulnerability in 9001 copyparty, published on 14 Jul 2023. 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-2023-37474 exists.

Affected packages and fixed versions:
- copyparty (PyPI): affected all versions; fixed in 1.8.2
- copyparty (PyPI): affected all versions; fixed in 1.8.2
- copyparty (PyPI): affected all versions; fixed in 1.8.2

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

## Sources

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

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