CVE-2025-58753
BaseFortify
Publication date: 2025-09-09
Last updated on: 2025-09-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 9001 | copyparty | to 1.19.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-552 | The product makes files or directories accessible to unauthorized actors, even though they should not be. |
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-58753 is a vulnerability in copyparty versions prior to 1.19.8 where a missing permission check in the shares feature (the 'shr' global option) allowed an attacker to access other files in the same folder as a shared single file by guessing their filenames. This unauthorized access was limited to sibling files within the folder and did not allow traversal into subdirectories or affect filekeys or dirkeys. The issue was fixed in version 1.19.8 by enforcing strict permission checks to restrict access only to the shared files. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized read access to files that were not explicitly shared but reside in the same folder as a shared file. An attacker with low privileges and network access could guess filenames to access sibling files, potentially exposing sensitive information. However, the vulnerability does not allow modification or deletion of files, nor does it permit access to subdirectories or cryptographic keys. The impact is limited to confidentiality with low severity. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to access sibling files within a shared folder when only a single file is supposed to be shared. Since the issue involves guessing filenames to access unauthorized files, you can test by accessing the file server shares and trying to retrieve files other than the explicitly shared one. Specific commands would depend on your environment and how copyparty is accessed (e.g., via HTTP requests or file browsing). For example, you could use curl or wget to request sibling filenames in the shared folder URL to see if unauthorized files are accessible. However, no explicit detection commands are provided in the available resources. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade copyparty to version 1.19.8 or later, where the vulnerability is fixed by enforcing strict permission checks on single-file shares. This update restricts access strictly to the shared files and prevents unauthorized access to sibling files. Until the upgrade can be applied, avoid creating shares for single files inside folders or restrict access to trusted users only. [1, 2, 3]