plone.namedfile vulnerable to Stored Cross Site Scripting with SVG images
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.6.1, 6.0.3, 6.1.3, 6.2.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
plone.namedfile allows users to handle `File` and `Image` fields targeting, but not depending on, Plone Dexterity content. Prior to versions 5.6.1, 6.0.3, 6.1.3, and 6.2.1, there is a stored cross site scripting vulnerability for SVG images. A security hotfix from 2021 already partially fixed this by making sure SVG images are always downloaded instead of shown inline. But the same problem still exists for scales of SVG images. Note that an image tag with an SVG image as source is not vulnerable, even when the SVG image contains malicious code. To exploit the vulnerability, an attacker would first need to upload an image, and then trick a user into following a specially crafted link. Patches are available in versions 5.6.1 (for Plone 5.2), 6.0.3 (for Plone 6.0.0-6.0.4), 6.1.3 (for Plone 6.0.5-6.0.6), and 6.2.1 (for Plone 6.0.7). There are no known workarounds.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- plone plone.namedfile
fixed in 5.6.1; From 6.0.0 · fixed in 6.0.3; From 6.1.0 · fixed in 6.1.3; From 6.2.0 · fixed in 6.2.1
- plone-namedfilePyPI
fixed in 5.6.1; From 6.0.0 · fixed in 6.0.3; From 6.1.0 · fixed in 6.1.3
- plone-namedfilePyPI
fixed in 5.6.1
- plone-namedfilePyPI
From 6.0.0 · fixed in 6.0.3
- plone-namedfilePyPI
From 6.1.0 · fixed in 6.1.3
- plone-namedfilePyPI
From 6.2.0 · fixed in 6.2.1