What is GHSA-GJ2H-2FPW-FHV9?

GHSA-GJ2H-2FPW-FHV9 is a medium-severity security vulnerability in @nuxt/ui (npm), affecting versions <= 4.7.1. No fixed version is listed yet.

Which versions of @nuxt/ui are affected by GHSA-GJ2H-2FPW-FHV9?

@nuxt/ui (npm) versions <= 4.7.1 is affected.

Is there a fix for GHSA-GJ2H-2FPW-FHV9?

No fixed version is listed for GHSA-GJ2H-2FPW-FHV9 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-GJ2H-2FPW-FHV9 exploitable, and should I be worried?

Whether GHSA-GJ2H-2FPW-FHV9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-GJ2H-2FPW-FHV9 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-GJ2H-2FPW-FHV9 in @nuxt/ui

Q: Which versions of @nuxt/ui are affected by GHSA-GJ2H-2FPW-FHV9?

@nuxt/ui (npm) versions <= 4.7.1 is affected.

Q: Is there a fix for GHSA-GJ2H-2FPW-FHV9?

No fixed version is listed for GHSA-GJ2H-2FPW-FHV9 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is GHSA-GJ2H-2FPW-FHV9 exploitable, and should I be worried?

Whether GHSA-GJ2H-2FPW-FHV9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-GJ2H-2FPW-FHV9 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Summary

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

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:

<component
  :is="parentBus ? 'div' : 'form'"
  :id="formId"
  ref="formRef"
  :class="ui({ class: [uiProp?.base, props.class] })"
  @submit.prevent="onSubmitWrapper"
>

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:

Create a minimal Nuxt app with a UAuthForm.
Build for production and visit in a browser with network throttling at 4G or slower.
Enter credentials.
Submit (or let autofill + Enter fire before hydration).

The URL becomes /login?email=…&password=…. Reproducible deterministically in Playwright by triggering submit immediately on load.

Credit

Reported by @nimonian. Originally filed as GHSA-92g7-2fpq-hmq8 against nuxt/nuxt; moved here because the affected code lives in @nuxt/ui.

Impact

Any application using UAuthForm (or UForm with credential-shaped fields) as documented. The cleartext password lands in:

the address bar,
window.history,
the Referer header of every same-origin subresource fetched from the resulting URL,
access logs of any reverse proxy, CDN, or WAF that records request URLs.

Affected versions

@nuxt/ui (<= 4.7.1)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Default the rendered <form> to method="post" so the pre-hydration fallback submits as POST rather than GET. Vue's @submit.prevent still intercepts the hydrated case; the attribute only matters in the race window. Applications that explicitly want native GET submission can opt back in by passing method="get".

Frequently Asked Questions

What is GHSA-GJ2H-2FPW-FHV9? GHSA-GJ2H-2FPW-FHV9 is a medium-severity security vulnerability in @nuxt/ui (npm), affecting versions <= 4.7.1. No fixed version is listed yet.
Which versions of @nuxt/ui are affected by GHSA-GJ2H-2FPW-FHV9? @nuxt/ui (npm) versions <= 4.7.1 is affected.
Is there a fix for GHSA-GJ2H-2FPW-FHV9? No fixed version is listed for GHSA-GJ2H-2FPW-FHV9 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-GJ2H-2FPW-FHV9 exploitable, and should I be worried? Whether GHSA-GJ2H-2FPW-FHV9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-GJ2H-2FPW-FHV9 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.