How severe is GHSA-62cr-6wp5-q43h?

GHSA-62cr-6wp5-q43h has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-62cr-6wp5-q43h?

GHSA-62cr-6wp5-q43h affects the following packages: copyparty (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-62cr-6wp5-q43h?

Update copyparty to 1.20.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-62cr-6wp5-q43h is resolved across your whole dependency graph.

How do I detect GHSA-62cr-6wp5-q43h in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for copyparty. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-62cr-6wp5-q43h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-62cr-6wp5-q43h?

O3 pinpoints whether GHSA-62cr-6wp5-q43h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-62cr-6wp5-q43h actively exploited in the wild?

No public exploit code has been indexed for GHSA-62cr-6wp5-q43h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-62cr-6wp5-q43h?

GHSA-62cr-6wp5-q43h has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 6th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-62cr-6wp5-q43h?

GHSA-62cr-6wp5-q43h is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-62cr-6wp5-q43h published, and has it been updated?

GHSA-62cr-6wp5-q43h was published on February 26, 2026 and was last updated on February 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-62cr-6wp5-q43h

MEDIUM

Copyparty vulnerable to reflected XSS via setck parameter

Also known asCVE-2026-27948

Published

Feb 26, 2026

Updated

Feb 26, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk6th percentile+0.12%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐍copyparty

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

An XSS allows for reflected cross-site scripting via URL-parameter ?setck=...

Details

A reflected cross-site scripting (XSS) vulnerability could allow an attacker to execute malicious javascript by tricking users into accessing a malicious link.

The worst-case outcome of this is being able to move or delete existing files on the server, or upload new files, using the account of the person who clicks the malicious link.

Indicators of Compromise

All attempted attacks (successful or not) would be logged to both the copyparty serverlog and the accesslog of the reverseproxy, and are detected by grep -E '[?&]setck=[^&"]*%' (the text setck= eventually followed by the % character).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`copyparty`	all versions	1.20.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for copyparty. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update copyparty to 1.20.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-62cr-6wp5-q43h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-62cr-6wp5-q43h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-62cr-6wp5-q43h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary An XSS allows for reflected cross-site scripting via URL-parameter `?setck=...` ### Details A reflected cross-site scripting (XSS) vulnerability could allow an attacker to execute malicious javascript by tricking users into accessing a malicious link. The worst-case outcome of this is being able to move or delete existing files on the server, or upload new files, using the account of the person who clicks the malicious link. ### Indicators of Compromise All attempted attacks (successful or not) would be logged to both the copyparty serverlog and the accesslog of the reverseproxy

O3 Security · Impact-Aware SCA

Is GHSA-62cr-6wp5-q43h in your dependencies?

O3 detects GHSA-62cr-6wp5-q43h across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works