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

Published Oct 6, 2026
·
Updated

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.

Affected Software

1 affected component
Quasar Quasar Framework<2.22.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Quasar Framework to a version that resolves this vulnerability.

    Fixed in 2.22.0

Event History

Oct 6, 2026
CVE Published
via MITRE·05:07 PM
Data Sourced
via MITRE·05:07 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Only server-side rendered Quasar deployments that use the SSR getHead() metadata serializer are affected. The client-side apply() path is not affected because it uses DOM APIs that encode attributes.

2

What must an attacker control to exploit this issue?

An attacker must be able to influence metadata passed through useMeta(), such as a post title, product name, excerpt, or display name. They can use that control to break out of the intended HTML text or quoted-attribute context and inject executable markup into the server-rendered response.

3

What version fixes the issue?

Upgrade Quasar Framework to version 2.22.0 or later. Versions prior to 2.22.0 are affected.

4

What can be done if an immediate upgrade is not possible?

Prevent untrusted or attacker-influenced values from being used in useMeta() fields rendered by SSR, or ensure those values are correctly encoded for their HTML text or quoted-attribute context before they reach the metadata serializer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203