copyparty has DOM-Based XSS vulnerability when displaying multimedia metadata
CVE-2025-54423GHSA-9q4r-x2hj-jmvr
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (copyparty 1.18.5), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI copyparty
- Affected
- <= 1.18.4
- Fixed in
- 1.18.5
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-9q4r-x2hj-jmvr lists affected ranges: PyPI copyparty >=0 <1.18.5 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-9q4r-x2hj-jmvr lists affected ranges: PyPI copyparty >=0 <=1.18.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
- EPSS
- CVE-2025-54423: 0.47% estimated exploitation activity in the next 30 days; percentile 40.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An unauthenticated attacker is able to execute arbitrary JavaScript code in a victim's browser due to improper sanitization of multimedia tags in music files, including m3u files. Details Multimedia metadata is rendered in the web-app without sanitization. This can be exploited in two ways: a user which has the necessary permission for uploading files can upload a song with an artist-name such as <img src=x onerror=alert(document.domain) an unauthenticated user can trick another user into clicking a malicious URL, performing this same exploit using an externally-hosted m3u file The CVE score and PoC is based on the m3u approach, which results in a higher severity. PoC 1. Create a file named song.m3u with the following content. Host this file on an attacker-controlled web server. 2. Craft and share the malicious URL: Impact Any user that accesses this malicious URL is impacted.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-9q4r-x2hj-jmvr
- Revision 1 · created ·
Published from osv record GHSA-9q4r-x2hj-jmvr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-54423 Advisory: copyparty has DOM-Based XSS vulnerability when displaying multimedia metadata IDs: CVE-2025-54423, GHSA-9q4r-x2hj-jmvr Record: https://patchnext.com/advisories/cve-2025-54423 (revision 2, source checked 26 Oct 2026, 13:32 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: copyparty 1.18.5. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI copyparty: affected <= 1.18.4; fixed in 1.18.5 ## Suggested inspection (read-only) - `python -m pip show copyparty`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on copyparty. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-9q4r-x2hj-jmvr (OSV record GHSA-9q4r-x2hj-jmvr lists affected ranges: PyPI copyparty >=0 <1.18.5 (fixed)) - Verified: https://github.com/advisories/GHSA-9q4r-x2hj-jmvr (GitHub-reviewed advisory GHSA-9q4r-x2hj-jmvr lists affected ranges: PyPI copyparty >=0 <=1.18.4) Commands are suggestions: review each one before running it.
Loading voting…