CVE-2023-41048: plone.namedfile vulnerable to Stored Cross Site Scripting with SVG images

Published Sep 21, 2023
·
Updated

Impact 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.

All versions of plone.namedfile are impacted.

Patches Patches will be released in various plone.namedfile releases:

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) 6.2.1 (for Plone 6.0.7)

Workarounds There is no workaround.

Other sources

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.

Affected Software

22 affected componentsFixes available
Plone namedfile<5.6.1
Plone plone=5.2
Plone namedfile>=6.0.0<6.0.3
Plone plone>=6.0.0<=6.0.4
Plone namedfile>=6.1.0<6.1.3
Plone plone=6.0.5
Plone plone=6.0.6
Plone namedfile=6.2.0
Plone plone=6.0.7
pip/plone.namedfile>=6.2.0<6.2.1
6.2.1
pip/plone.namedfile>=6.1.0<6.1.3
6.1.3
pip/plone.namedfile>=6.0.0<6.0.3
6.0.3
pip/plone.namedfile<5.6.1
5.6.1
All of the following
Plone namedfile<5.6.1
Plone plone=5.2
All of the following
Plone namedfile>=6.0.0<6.0.3
Plone plone>=6.0.0<=6.0.4
All of the following
Plone namedfile>=6.1.0<6.1.3
Any of the following
Plone plone=6.0.5
Plone plone=6.0.6
All of the following
Plone namedfile=6.2.0
Plone plone=6.0.7

Event History

Sep 21, 2023
CVE Published
via MITRE·02:31 PM
Data Sourced
via MITRE·02:31 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
05:14 PM
Data Sourced
via GitHub·05:14 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the impact of CVE-2023-41048?

The impact of CVE-2023-41048 is a stored cross site scripting vulnerability for SVG images.

2

Is there a fix available for CVE-2023-41048?

Yes, a security hotfix from 2021 partially fixed this vulnerability by ensuring SVG images are downloaded instead of shown inline.

3

Which versions of plone.namedfile are affected by CVE-2023-41048?

Versions 6.2.0 to 6.2.1, 6.1.0 to 6.1.3, 6.0.0 to 6.0.3, and up to version 5.6.1 of plone.namedfile are affected by CVE-2023-41048.

4

What is the severity of CVE-2023-41048?

The severity of CVE-2023-41048 is low.

5

What are the references for CVE-2023-41048?

The references for CVE-2023-41048 are [security advisory](https://github.com/plone/plone.namedfile/security/advisories/GHSA-jj7c-jrv4-c65x), [NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-41048), and [commit on GitHub](https://github.com/plone/plone.namedfile/commit/188f66a4577021cf8f2bf7c0f5150f9b9573f167).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203