CKAN has an XSS vector in user uploaded images in group/org and user profilesGHSA-7pq5-qcp6-mcww
HIGHFix: ckan/ckan@7da6a26GHSA-7pq5-qcp6-mcww is a high-severity (CVSS 7.3) Cross-site Scripting (XSS) vulnerability in ckan. A fix is available for ckan — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7pq5-qcp6-mcww.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
ckan🐍ckanReal-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
Impact
Using a specially crafted file, a user could potentially upload a file containing code that when executed could send arbitrary requests to the server. If that file was opened by an administrator, it could lead to escalation of privileges of the original submitter or other malicious actions. Users must have been registered to the site to exploit this vulnerability.
Patches
This vulnerability has been fixed in CKAN 2.10.7 and 2.11.2
Workarounds
On versions prior to CKAN 2.10.7 and 2.11.2, site maintainers can restrict the file types supported for uploading using the ckan.upload.user.mimetypes / ckan.upload.user.types and ckan.upload.group.mimetypes / ckan.upload.group.types config options. To entirely disable file uploads you can use:
ckan.upload.user.types = none
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ckan | all versions | 2.10.7pip install --upgrade 'ckan==2.10.7' |
| 🐍PyPI | ckan | ≥ 2.11.0&&< 2.11.2 | 2.11.2pip install --upgrade 'ckan==2.11.2' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckan, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ckan to 2.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7pq5-qcp6-mcww is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-7pq5-qcp6-mcww in your dependencies?
Find it across PyPI, including transitive dependencies.