CVE-2022-4495: A vulnerability, which was classified as problematic, has been found in collective.dms.basecontent up to 1.6

Q: How do I fix CVE-2022-4495?

collective.dms.basecontent: upgrade to 1.7. Exact commands for each OS are on this page.

Q: Is CVE-2022-4495 being exploited?

CVE-2022-4495 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-4495 affect?

CVE-2022-4495 affects collective.dms.basecontent. Severity is low (CVSS 3.5). 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

Q: How urgent is CVE-2022-4495?

Priority 23/100. No elevated risk signals yet.

Routine

LOW 3.5UPGRADE

CVE-2022-4495 is a low-severity flaw (CVSS 3.5) affecting collective.dms.basecontent. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 upgra

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.5 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-12-14
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: collective.dms.basecontent project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-14 15:15 UTCPublished CVE record published
2026-06-17 05:21 UTCUpdated Record last modified

collective.dms.basecontent project collective.dms.basecontent UPGRADE

Affected: < 1.7

Fixed in: 1.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy collective.dms.basecontent || rpm -q collective.dms.basecontent || collective.dms.basecontent --version

2. UPGRADE to 1.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade collective.dms.basecontent

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade collective.dms.basecontent

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-4495?

collective.dms.basecontent: upgrade to 1.7. Exact commands for each OS are on this page.

Is CVE-2022-4495 being exploited?

CVE-2022-4495 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-4495 affect?

CVE-2022-4495 affects collective.dms.basecontent. Severity is low (CVSS 3.5). 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

How urgent is CVE-2022-4495?

Priority 23/100. No elevated risk signals yet.

References

← Back to latest CVEs