GHSA-gj2h-2fpw-fhv9: @nuxt/ui: UAuthForm / UForm SSR markup omits `method`, leaking credentials via GET if submitted before hydration
The @nuxt/ui package's UForm and UAuthForm components render server-side forms without a method attribute, relying on client-side hydration to intercept submissions. If a user submits the form before hydration completes, the browser defaults to a GET request, sending form data including passwords in the URL query string. This can expose credentials in the address bar, browser history, Referer headers, and server logs. The issue affects versions up to and including 4.7.1. A patch involves setting the form's method attribute to POST by default to prevent credential leakage during the hydration race window.
AI Analysis
Technical Summary
The vulnerability in @nuxt/ui's UForm and UAuthForm components arises because server-side rendered forms omit the method attribute and rely on a Vue hydration handler to prevent native form submission. If the form is submitted before hydration (e.g., due to slow network or JS blocking), the browser performs a default GET request, including sensitive fields like passwords in the URL query string. This leads to credential leakage via the URL, browser history, Referer headers, and logs. The recommended fix is to default the form's method attribute to POST to ensure safe fallback behavior prior to hydration.
Potential Impact
Credentials, including passwords, can be exposed in cleartext in the URL query string if a form is submitted before Vue hydration attaches the submit handler. This exposure affects the browser address bar, window history, Referer headers sent to same-origin resources, and any server or proxy logs that record URLs. This leakage risks unauthorized disclosure of sensitive authentication data.
Mitigation Recommendations
A patch is available that sets the form's method attribute to POST by default, preventing credential leakage during the hydration race window. Applications can opt back into GET submissions by explicitly specifying method="get". Users should upgrade to a version where this fix is applied or manually set method="post" on forms using UForm or UAuthForm to mitigate the issue.
GHSA-gj2h-2fpw-fhv9: @nuxt/ui: UAuthForm / UForm SSR markup omits `method`, leaking credentials via GET if submitted before hydration
Description
The @nuxt/ui package's UForm and UAuthForm components render server-side forms without a method attribute, relying on client-side hydration to intercept submissions. If a user submits the form before hydration completes, the browser defaults to a GET request, sending form data including passwords in the URL query string. This can expose credentials in the address bar, browser history, Referer headers, and server logs. The issue affects versions up to and including 4.7.1. A patch involves setting the form's method attribute to POST by default to prevent credential leakage during the hydration race window.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in @nuxt/ui's UForm and UAuthForm components arises because server-side rendered forms omit the method attribute and rely on a Vue hydration handler to prevent native form submission. If the form is submitted before hydration (e.g., due to slow network or JS blocking), the browser performs a default GET request, including sensitive fields like passwords in the URL query string. This leads to credential leakage via the URL, browser history, Referer headers, and logs. The recommended fix is to default the form's method attribute to POST to ensure safe fallback behavior prior to hydration.
Potential Impact
Credentials, including passwords, can be exposed in cleartext in the URL query string if a form is submitted before Vue hydration attaches the submit handler. This exposure affects the browser address bar, window history, Referer headers sent to same-origin resources, and any server or proxy logs that record URLs. This leakage risks unauthorized disclosure of sensitive authentication data.
Mitigation Recommendations
A patch is available that sets the form's method attribute to POST by default, preventing credential leakage during the hydration race window. Applications can opt back into GET submissions by explicitly specifying method="get". Users should upgrade to a version where this fix is applied or manually set method="post" on forms using UForm or UAuthForm to mitigate the issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gj2h-2fpw-fhv9
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a46ecb527e9c7971943c89d
Added to database: 07/02/2026, 22:56:53 UTC
Last enriched: 07/02/2026, 23:09:33 UTC
Last updated: 07/02/2026, 23:09:33 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.