Nuxt UI forms expose submitted credentials in URL before hydration
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- High
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-200.
Summary
Nuxt UI before 4.8.1 renders UForm and UAuthForm server markup without a method attribute (CWE-598). If a user submits before Vue hydration completes or the client bundle is unavailable, the browser places the named fields, including passwords, in the URL query string. An attacker who can read those logs, browser history or Referer headers can get the credentials, but the attack needs user interaction and high complexity conditions. SSVC rates exploitation as proof of concept.
Written with Claude Haiku 5.5 from the sources below · 2026-11-14
Description from the CNA
Nuxt UI is an intuitive Vue UI library powered by Reka UI and Tailwind CSS. Prior to 4.8.1, the server-rendered form element produced by UForm in src/runtime/components/Form.vue omits the method and action attributes and relies solely on the hydrated @submit.prevent handler to stop native submission. UAuthForm composes UForm and can render named credential fields, including an input with type password, inside the same markup. If a user submits before Vue hydration completes, or when the client bundle is blocked or unavailable, the browser performs its default GET submission and serializes the named fields into the current URL query string. The credentials can then appear in the address bar, browser history, reverse-proxy, CDN, or WAF request logs, and Referer headers sent with same-origin subresource requests. This issue is fixed in version 4.8.1.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Nuxt UI to version 4.8.1, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-14
- Fix · CNA ui (nuxt) Fixed in 4.8.1
Timeline
- 2026-11-09 Threatist record created from CVE-2026-123808
- 2026-11-14 CISA SSVC decision points changed
References
More nuxt vulnerabilities
- TI-2023-03020 Code Injection in nuxt/nuxt CVSS 3.1CRITICAL 9.8
- TI-2024-28339 Server-Side Request Forgery (SSRF) in nuxt-icon CVSS 3.1HIGH 8.6
- TI-2024-22685 Remote code execution via the browser when running the test locally in nuxt CVSS 3.1HIGH 8.8
- TI-2026-86049 Unauthenticated SQLite function DoS in Nuxt Content query API CVSS 3.1HIGH 7.5
- TI-2026-26689 Nuxt OG Image vulnerable to DoS via image generation CVSS 4.0MEDIUM 6.9
- TI-2022-04037 Cross-site Scripting (XSS) - DOM in nuxt/framework CVSS 3.1MEDIUM 6.1
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences