CVE-2023-37474High· 7.5▾ MidnightPoC availablecopyparty vulnerable to path traversal attack
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 41.3 · likelihood 9 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Public exploit / PoC code seen in 2 sources. Availability, not in-the-wild use.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
45%
1 GitHub repo · Nuclei ×1 (last check)
All versions before 1.8.2 have a path traversal vulnerability, allowing an attacker to download unintended files from the server.
Unauthenticated users were able to retrieve any files which are accessible (according to OS-level permissions) from the copyparty process. Usually, this is all files that are readable by the OS account which is used to run copyparty.
The vulnerability did not make it possible to list the contents of folders, so an attacker needs to know the full absolute path to the file, or the relative path from where copyparty is installed.
Some methods of running copyparty (prisonparty, the nix package, and docker) had a mitigating effect, mostly reducing the attack scope to files inside copyparty volumes, and possibly the copyparty config file.
Please keep in mind that, if an attacker were to find a way to overwrite the logs, for example by discovering the password to another service with sufficient privileges, then the following approaches cannot be trusted.
if copyparty was only accessible through a reverse proxy, then all attacks would be visible in the webserver access-log as URLs which contain both .cpr/ and %2F
(gzip -dc access.log*.gz; cat access.log) | sed -r 's/" [0-9]+ .*//' | grep -E 'cpr/.*%2[^0]' | grep -vF data:image/svg
However, if copyparty was directly accessible from the internet, then any successful attacks (file retrievals) would unfortunately leave no trace. That said, it is very probable that an attacker would make at least one invalid attempt, which would become apparent in the copyparty server log, detectable with grep -aE '(Errno|Permission).*\.cpr/' revealing the following:
[IOError] [Errno 13] Permission denied: '/etc/shadow', .cpr//etc/shadow[PermissionError] [Errno 13] Permission denied: b'/etc/shadow', .cpr//etc/shadowProviding an exact command for this approach is difficult, as it depends on how copyparty is deployed;
journalctl -am | grep -aE '(Errno|Permission).*\.cpr/'xz -kdc thefilename.xz | grep -aE '(Errno|Permission).*\.cpr/'grep -aE '(Errno|Permission).*\.cpr/' thefilename.txtcurl -sik http://127.0.0.1:3923/.cpr/%2Fetc%2Fpasswd
curl -sik http://127.0.0.1:3923/.cpr/..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd
copyparty < 1.8.2Upgrade to a patched release:
copyparty 1.8.2Connected by shared product, vendor, weakness, or advisory.
CVE-2025-54589Medium· 6.3copyparty Reflected XSS via Filter Parameter
CVE-2023-41471High· 7.8Cross Site Scripting vulnerability in copyparty before 1.9.2 allows a local attacker to execute arbitrary code via a crafted payload to t…
CVE-2026-30974Medium· 4.6copyparty: volflag `nohtml` did not block javascript in svg files
CVE-2026-27948Medium· 5.4Copyparty vulnerable to reflected XSS via setck parameter
CVE-2025-58753Mediumcopyparty: Sharing a single file does not fully restrict access to other files in source folder
CVE-2025-27145Low· 3.6copyparty renders unsanitized filenames as HTML when user uploads empty files