# CVE-2022-39239: @netlify/ipx vulnerable to Full Response SSRF and Stored XSS via Cache Poisoning and Improper Host Validation > Attackers can bypass domain allowlists to fetch arbitrary images via SSRF and inject malicious scripts through cached SVGs, leading to XSS. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 23 Sep 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-9jjv-524m-jm98 ## What is CVE-2022-39239? CVE-2022-39239 is a medium-severity server-side request forgery vulnerability in netlify-ipx, published on 23 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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 `` 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. Weakness: CWE-918 (Server-Side Request Forgery), CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2022-39239? 2 open source packages ship an affected version, including @netlify/ipx. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@netlify/ipx` | npm | All versions | 1.2.3 | | `@netlify/ipx` | npm | All versions | 1.2.3 | Products: Nuxtjs Netlify-Ipx. ## How do I fix CVE-2022-39239? Upgrade @netlify/ipx to 1.2.3 or later. ## Is CVE-2022-39239 being exploited? There is no known exploitation of CVE-2022-39239 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-39239 and fix it if it is affected. What it is: CVE-2022-39239 is a medium-severity server-side request forgery vulnerability in netlify-ipx, published on 23 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-39239 in the wild and no public exploit code. Affected packages and fixed versions: - @netlify/ipx (npm): affected all versions; fixed in 1.2.3 - @netlify/ipx (npm): affected all versions; fixed in 1.2.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-39239/ (Markdown: https://insights.sbomify.com/CVE-2022-39239/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39239 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39239 - OSV: https://osv.dev/vulnerability/CVE-2022-39239 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-39239/ Summaries are generated and may contain mistakes; the official description above is the record.