How severe is CVE-2023-41048?

CVE-2023-41048 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-41048?

CVE-2023-41048 affects the following packages: plone-namedfile (PyPI), plone-namedfile (PyPI), plone-namedfile (PyPI), plone-namedfile (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2023-41048?

Update plone-namedfile to 5.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41048 is resolved across your whole dependency graph.

How do I detect CVE-2023-41048 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone-namedfile, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-41048 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2023-41048 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-41048 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-41048?

CVE-2023-41048 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-41048?

CVE-2023-41048 is classified as Cross-site Scripting (XSS) (CWE-79), CWE-80 (CWE-80). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2023-41048 published, and has it been updated?

CVE-2023-41048 was published on September 21, 2023 and was last updated on November 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

LOW severity

CVE-2023-41048 — plone-namedfile

LOWFix: plone/plone.namedfile@188f66a

CVE-2023-41048 is a low-severity (CVSS 3.7) Cross-site Scripting (XSS) vulnerability in plone-namedfile. A fix is available for plone-namedfile — see the affected versions and patch details below.

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

Also known asGHSA-jj7c-jrv4-c65xPYSEC-2023-311

Published

Sep 21, 2023

Updated

Nov 3, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-41048.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐍plone-namedfile🐍plone-namedfile🐍plone-namedfile🐍plone-namedfile

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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 Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`plone-namedfile`	all versions	5.6.1`pip install --upgrade 'plone-namedfile==5.6.1'`
🐍PyPI	`plone-namedfile`	≥ 6.0.0&&< 6.0.3	6.0.3`pip install --upgrade 'plone-namedfile==6.0.3'`
🐍PyPI	`plone-namedfile`	≥ 6.1.0&&< 6.1.3	6.1.3`pip install --upgrade 'plone-namedfile==6.1.3'`
🐍PyPI	`plone-namedfile`	≥ 6.2.0&&< 6.2.1	6.2.1`pip install --upgrade 'plone-namedfile==6.2.1'`

Affected Products

1 product · 4 configurations

Application

namedfileplone

≥ 6.1.0 && < 6.1.3

1 version

6.2.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone-namedfile, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update plone-namedfile to 5.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41048 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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 f

O3 Security · Impact-Aware SCA

Is CVE-2023-41048 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works