CVE-2025-54423
BaseFortify
Publication date: 2025-07-28
Last updated on: 2025-09-22
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 9001 | copyparty | to 1.18.5 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-54423 is a DOM-Based Cross-Site Scripting (XSS) vulnerability in the copyparty file server (versions up to 1.18.4). It occurs because the application improperly sanitizes multimedia metadata tags in music files, including m3u playlists. This allows an attacker to inject and execute arbitrary JavaScript code in the browsers of users who view the affected media or click on malicious URLs. The vulnerability can be exploited either by uploading a malicious media file or by tricking a user into loading a malicious externally-hosted m3u playlist. The issue is fixed in version 1.18.5 by properly escaping metadata fields before rendering them in the web interface. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute arbitrary JavaScript code in your browser when you access the affected copyparty server. This can lead to unauthorized actions such as stealing session cookies, performing actions on your behalf, or displaying malicious content. The attack requires user interaction, such as clicking a malicious URL or viewing a malicious media file on the server. The impact includes limited confidentiality and integrity risks but no availability impact. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if your copyparty server version is 1.18.4 or earlier, as these versions are vulnerable. You can also look for suspicious m3u playlist files or multimedia files with unusual or malicious metadata tags that might contain JavaScript payloads. To detect exploitation attempts, monitor HTTP requests for URLs containing m3u parameters pointing to external sources, such as URLs like `http://yourserver/#m3u=https://malicious.example.com/song.m3u`. There are no specific commands provided in the resources, but you can verify the version by checking the copyparty version with your package manager or by running the server and checking its version output. Additionally, inspecting uploaded media files for suspicious metadata or scanning logs for unusual URL parameters related to m3u files can help detect attempts. [3]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, upgrade your copyparty installation to version 1.18.5 or later, where the issue is fixed. The fix sanitizes and escapes multimedia metadata fields to prevent script injection. Additionally, the update blocks external m3u files and enhances cookie security by setting the SameSite attribute to Strict by default, which helps mitigate CSRF attacks. If upgrading immediately is not possible, restrict or disable the media-indexing feature and prevent uploading or loading of external m3u playlist files to reduce exposure. [1, 2]