Netlify Ipx

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:nuxtjs:netlify-ipx:*:*:*:*:*:node.js:*:*

part: a version: * update: *

VendorNuxtjs (acd7643c-bab4-57d8-9310-e9b654e0ba7d)
ProductNetlify Ipx (ce6d5aeb-05e4-5de9-a12e-6b3091149526)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/netlify/netlify-ipx purl2cpe 2026-06-01 10:16:52.377625
pkg:npm/%40netlify/ipx purl2cpe 2026-06-01 10:16:52.377628

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2022-39239 vulnerable 2026-06-08 05:47:18.410671 nefly-ipx subject to Server-Side Request Forgery and Stored Cross-Site Scripting via Cache Poisoning and Improper Host Validation
MEDIUM (6.1)
netlify-ipx is an on-Demand image optimization for Netlify using ipx. In versions prior to 1.2.3, an attacker can bypass the source image domain allowlist by sending specially crafted headers, causing the handler to load and return arbitrary images. Because the response is cached globally, this image will then be served to visitors without requiring those headers to be set. XSS can be achieved by requesting a malicious SVG with embedded scripts, which would then be served from the site domain. Note that this does not apply to images loaded in `<img>` tags, as scripts do not execute in this context. The image URL can be set in the header independently of the request URL, meaning any site images that have not previously been cached can have their cache poisoned. This problem has been fixed in version 1.2.3. As a workaround, cached content can be cleared by re-deploying the site.
Published: 2022-09-23T07:55:08.000Z
Updated: 2025-04-23T16:56:05.928Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.