CVE-2023-41048

plone.namedfile vulnerable to Stored Cross Site Scripting with SVG images

Workarounds

There is no workaround.

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2023-41048 has a CVSS score of 3.7 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.6.1, 6.0.3, 6.1.3, 6.2.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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)

1. What is CVE-2023-41048? CVE-2023-41048 is a low-severity cross-site scripting (XSS) vulnerability in plone.namedfile (pip), affecting versions < 5.6.1. It is fixed in 5.6.1, 6.0.3, 6.1.3, 6.2.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2023-41048? CVE-2023-41048 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of plone.namedfile are affected by CVE-2023-41048? plone.namedfile (pip) versions < 5.6.1 is affected.
4. Is there a fix for CVE-2023-41048? Yes. CVE-2023-41048 is fixed in 5.6.1, 6.0.3, 6.1.3, 6.2.1. Upgrade to this version or later.
5. Is CVE-2023-41048 exploitable, and should I be worried? Whether CVE-2023-41048 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-41048 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-41048?
   • Upgrade plone.namedfile to 5.6.1 or later
   • Upgrade plone.namedfile to 6.0.3 or later
   • Upgrade plone.namedfile to 6.1.3 or later
   • Upgrade plone.namedfile to 6.2.1 or later