Skip to content

← Actionable
Medium, CVSS 6.9amended

@nuxt/ui: UAuthForm / UForm SSR markup omits method, leaking credentials via GET if submitted before hydration

GHSA-gj2h-2fpw-fhv9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nuxt/ui 4.8.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm @nuxt/ui

    Affected
    < 4.8.1
    Fixed in
    4.8.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary UForm and UAuthForm render a server-side <form element with no method and no action attribute, relying on a hydrated @submit.prevent handler to intercept submission. If a user submits the form before Vue hydration has attached the handler (autofill plus Enter on a slow network, JS bundle blocked by CSP or CDN failure, etc.), the browser performs the native default: a GET to the current URL with every named field, including <input type="password", serialised into the query string. Details src/runtime/components/Form.vue (around the template's <form element) emits: No method, no action. @submit.prevent is the only thing stopping native submission, and it only exists after hydration. UAuthForm composes UForm and inherits the same shape. The SSR snapshot of UAuthForm (test/components/snapshots/AuthForm.spec.ts.snap) shows the rendered markup, with <input type="password" name="password" inside a <form that has no method. Proof of concept Reported by @nimonian: 1. Create a minimal…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-gj2h-2fpw-fhv9

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-gj2h-2fpw-fhv9

Agent brief

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

# Patch Next advisory brief: GHSA-gj2h-2fpw-fhv9

Advisory: @nuxt/ui: UAuthForm / UForm SSR markup omits `method`, leaking credentials via GET if submitted before hydration
IDs: GHSA-gj2h-2fpw-fhv9
Record: https://patchnext.com/advisories/ghsa-gj2h-2fpw-fhv9 (revision 3, source checked 26 Oct 2026, 13:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @nuxt/ui 4.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nuxt/ui: affected < 4.8.1; fixed in 4.8.1

## Suggested inspection (read-only)
- `npm ls @nuxt/ui --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/ui.
- 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-gj2h-2fpw-fhv9 (OSV record GHSA-gj2h-2fpw-fhv9 lists affected ranges: npm @nuxt/ui >=0 <4.8.1 (fixed))
- Verified: https://github.com/advisories/GHSA-gj2h-2fpw-fhv9 (GitHub-reviewed advisory GHSA-gj2h-2fpw-fhv9 lists affected ranges: npm @nuxt/ui >=0 <4.8.1)

Commands are suggestions: review each one before running it.

Loading voting…