GHSA-jj7c-jrv4-c65x
LOWplone.namedfile vulnerable to Stored Cross Site Scripting with SVG images
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
plone-namedfile🐍plone-namedfile🐍plone-namedfile🐍plone-namedfileReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | plone-namedfile | all versions | 5.6.1 |
| 🐍PyPI | plone-namedfile | ≥ 6.0.0&&< 6.0.3 | 6.0.3 |
| 🐍PyPI | plone-namedfile | ≥ 6.1.0&&< 6.1.3 | 6.1.3 |
| 🐍PyPI | plone-namedfile | ≥ 6.2.0&&< 6.2.1 | 6.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone-namedfile. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update plone-namedfile to 5.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jj7c-jrv4-c65x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jj7c-jrv4-c65x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-jj7c-jrv4-c65x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jj7c-jrv4-c65x in your dependencies?
O3 detects GHSA-jj7c-jrv4-c65x across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.