Quasar Framework: Stored/Reflected XSS via unescaped SSR meta tag rendering in getHead()

Why it is Amber

• CVSS 10.0 critical
• Remotely exploitable without logging in
• On your watchlist: npm

Affected packages

References

• https://github.com/advisories/GHSA-pq96-jpmf-w254
• https://github.com/quasarframework/quasar/security/advisories/GHSA-pq96-jpmf-w254
• https://nvd.nist.gov/vuln/detail/CVE-2026-106102
• https://github.com/quasarframework/quasar/commit/11505afe5b5218f2c468f130181815b898fd1e40
• https://github.com/quasarframework/quasar/releases/tag/quasar-v2.22.0
• https://github.com/advisories/GHSA-pq96-jpmf-w254

Original description

Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to 2.22.0, the SSR-only getHead() serializer in ui/src/plugins/meta/Meta.js used getAttr() to interpolate values supplied through useMeta() into title, meta, link, and script markup without HTML text or quoted-attribute encoding. injectServerMeta() appended that output to the raw server-rendered response. An attacker who can influence dynamic page metadata, such as a post title, product name, excerpt, or display name, can terminate the intended HTML context and inject executable markup before hydration. The client-side apply() path is not affected because it uses DOM APIs that encode attributes. This issue is fixed in version 2.22.0.