Skip to content

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

Low severity GitHub Reviewed Published Sep 21, 2023 in plone/plone.namedfile • Updated Apr 10, 2025

Package

pip plone.namedfile (pip)

Affected versions

< 5.6.1
>= 6.0.0, < 6.0.3
>= 6.1.0, < 6.1.3
>= 6.2.0, < 6.2.1

Patched versions

5.6.1
6.0.3
6.1.3
6.2.1

Description

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.

References

@mauritsvanrees mauritsvanrees published to plone/plone.namedfile Sep 21, 2023
Published by the National Vulnerability Database Sep 21, 2023
Published to the GitHub Advisory Database Sep 21, 2023
Reviewed Sep 21, 2023
Last updated Apr 10, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(65th percentile)

Weaknesses

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Learn more on MITRE.

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as <, >, and & that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Learn more on MITRE.

CVE ID

CVE-2023-41048

GHSA ID

GHSA-jj7c-jrv4-c65x

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.