Summary
useHeadSafe() can be bypassed to inject arbitrary HTML attributes, including event handlers, into SSR-rendered <head> tags. This is the composable that Nuxt docs recommend for safely handling user-generated content.
Details
XSS via data-* attribute name injection
The acceptDataAttrs function (safe.ts, line 16-20) allows any property key starting with data- through to the final HTML. It only checks the prefix, not whether the key contains spaces or other characters that break HTML attribute parsing.
function acceptDataAttrs(value: Record<string, string>) {
return Object.fromEntries(
Object.entries(value || {}).filter(([key]) => key === 'id' || key.startsWith('data-')),
)
}This result gets merged into every tag's props at line 114:
tag.props = { ...acceptDataAttrs(prev), ...next }Then propsToString (propsToString.ts, line 26) interpolates property keys directly into the HTML string with no sanitization:
attrs += value === true ? ` ${key}` : ` ${key}="${encodeAttribute(value)}"`A space in the key breaks out of the attribute name. Everything after the space becomes separate HTML attributes.
PoC
The most practical vector uses a link tag. <link rel="stylesheet"> fires onload once the stylesheet loads, giving reliable script execution:
useHeadSafe({
link: [{
rel: 'stylesheet',
href: '/valid-stylesheet.css',
'data-x onload=alert(document.domain) y': 'z'
}]
})SSR output:
<link data-x onload=alert(document.domain) y="z" rel="stylesheet" href="/valid-stylesheet.css">
The browser parses onload=alert(document.domain) as its own attribute. Once the stylesheet loads, the handler fires.
The same injection works on any tag type since acceptDataAttrs is applied to all of them at line 114. Here's the same thing on a meta tag (the injected attributes render, though onclick doesn't fire on non-interactive <meta> elements):
useHeadSafe({
meta: [{
name: 'description',
content: 'legitimate content',
'data-x onclick=alert(document.domain) y': 'z'
}]
})Realistic scenario
A Nuxt app accepts SEO metadata from a CMS or user profile. The developer uses useHeadSafe() as the docs recommend. An attacker puts a data-* key with spaces and an event handler into their input. The payload renders into the HTML on every page load.
Suggested fix
For vulnerability 1, validate that attribute names only contain characters legal in HTML attributes:
const SAFE_ATTR_RE = /^[a-zA-Z][a-zA-Z0-9\-]*$/
function acceptDataAttrs(value: Record<string, string>) {
return Object.fromEntries(
Object.entries(value || {}).filter(
([key]) => (key === 'id' || key.startsWith('data-')) && SAFE_ATTR_RE.test(key)
),
)
}
simonkoeck Reporter
Summary
useHeadSafe()can be bypassed to inject arbitrary HTML attributes, including event handlers, into SSR-rendered<head>tags. This is the composable that Nuxt docs recommend for safely handling user-generated content.Details
XSS via
data-*attribute name injectionThe
acceptDataAttrsfunction (safe.ts, line 16-20) allows any property key starting withdata-through to the final HTML. It only checks the prefix, not whether the key contains spaces or other characters that break HTML attribute parsing.This result gets merged into every tag's props at line 114:
Then
propsToString(propsToString.ts, line 26) interpolates property keys directly into the HTML string with no sanitization:A space in the key breaks out of the attribute name. Everything after the space becomes separate HTML attributes.
PoC
The most practical vector uses a
linktag.<link rel="stylesheet">firesonloadonce the stylesheet loads, giving reliable script execution:SSR output:
The browser parses
onload=alert(document.domain)as its own attribute. Once the stylesheet loads, the handler fires.The same injection works on any tag type since
acceptDataAttrsis applied to all of them at line 114. Here's the same thing on ametatag (the injected attributes render, thoughonclickdoesn't fire on non-interactive<meta>elements):Realistic scenario
A Nuxt app accepts SEO metadata from a CMS or user profile. The developer uses
useHeadSafe()as the docs recommend. An attacker puts adata-*key with spaces and an event handler into their input. The payload renders into the HTML on every page load.Suggested fix
For vulnerability 1, validate that attribute names only contain characters legal in HTML attributes: