Nuxt OG Image vulnerable to Server-Side Request Forgery via user-controlled parameters

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Product: Nuxt OG Image Version: < 6.2.5 CWE-ID: CWE-918: Server-Side Request Forgery Description The image generation endpoint (/og/d/) accepts user-controlled parameters that are passed to the server-side renderer without proper validation or filtering. An attacker can trigger server-side requests to internal network addresses through multiple vectors. Impact - Scanning internal ports and services inaccessible from the outside - Reading sensitive data from cloud infrastructure metadata services (tokens, credentials) when verbose error output is enabled Attack Vectors Three distinct vectors were identified, all exploiting the same underlying lack of URL validation: Vector 1: CSS background-image injection via style parameter Vector 2: <img src injection via html parameter When verbose errors are enabled, the response content is leaked in base64-encoded error messages. Vector 3: SVG <image href injection via html parameter Mitigation Fixed in v6.2.5. The image source plugin now blocks…

Published by the source

31 Mar 2026, 23:26 UTC

Last modified by the source

31 Mar 2026, 23:34 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pqhr-mp3f-hrpp

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pqhr-mp3f-hrpp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-pqhr-mp3f-hrpp

Advisory: Nuxt OG Image vulnerable to Server-Side Request Forgery via user-controlled parameters
IDs: GHSA-pqhr-mp3f-hrpp
Record: https://patchnext.com/advisories/ghsa-pqhr-mp3f-hrpp (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt-og-image 6.2.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt-og-image: affected < 6.2.5; fixed in 6.2.5

## Suggested inspection (read-only)
- `npm ls nuxt-og-image --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt-og-image.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pqhr-mp3f-hrpp (OSV record GHSA-pqhr-mp3f-hrpp lists affected ranges: npm nuxt-og-image >=0 <6.2.5 (fixed))
- Verified: https://github.com/advisories/GHSA-pqhr-mp3f-hrpp (GitHub-reviewed advisory GHSA-pqhr-mp3f-hrpp lists affected ranges: npm nuxt-og-image >=0 <6.2.5)

Commands are suggestions: review each one before running it.