plone.namedfile vulnerable to Stored Cross Site Scripting with SVG images
plone.namedfile
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| plone-namedfile PyPI |
|
|
plone.namedfile
| Product | Affected | Fixed in |
|---|---|---|
| plone-namedfile PyPI |
|
|
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.
From the CVE record · GitHub_M
SVG image scales in plone.namedfile are vulnerable to stored cross-site scripting. An attacker must first upload an SVG image and then trick a user into following a specially crafted link; the input does not specify what access is needed to upload the image.
Check installations using the PyPI plone-namedfile package in versions below 5.6.1, 6.0.0 through 6.0.2, 6.1.0 through 6.1.2, or 6.2.0.