CVE-2022-4495 is a low-severity (CVSS 3.5) Cross-site Scripting (XSS) vulnerability in collective-dms-basecontent. A fix is available for collective-dms-basecontent — see the affected versions and patch details below.
collective.dms.basecontent column.py renderCell cross site scripting
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
collective-dms-basecontentReal-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
A vulnerability, which was classified as problematic, has been found in collective.dms.basecontent up to 1.6. This issue affects the function renderCell of the file src/collective/dms/basecontent/browser/column.py. The manipulation leads to cross site scripting. The attack may be initiated remotely. Upgrading to version 1.7 is able to address this issue. The name of the patch is 6c4d616fcc771822a14ebae5e23f3f6d96d134bd. It is recommended to upgrade the affected component. The identifier VDB-215813 was assigned to this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | collective-dms-basecontent | all versions | 1.7pip install --upgrade 'collective-dms-basecontent==1.7' |
Affected Products
collective.dms.basecontentcollective.dms.basecontent_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for collective-dms-basecontent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update collective-dms-basecontent to 1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4495 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 CVE-2022-4495 in your dependencies?
Find it across PyPI, including transitive dependencies.