pypi package report

Is plone-namedfile safe?

1 known vulnerability, worst severity LOW.

// reach

20 direct dependencies

4 carry known advisories, worst CRITICAL

23 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage

No published models are known to use this package.


cvss
0.0
low

severity out of 10

epss
0.00%
medium

chance of exploitation in 30 days, 46th percentile of all CVEs

xyz score
0.0
low

CyberXYZ composite out of 10

fig. 01 — GHSA-jj7c-jrv4-c65x, the advisory selected below

// 1 advisories

GHSA-jj7c-jrv4-c65x

LOWCVE-2023-41048
// 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.

// cvss v3.1 vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

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

Checked 2026-10-23 at 18:53 UTC. The most recent advisory here was published 2023-09-21. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.