Skip to main content
VulnerabilityPublished

CVE-2026-106102: quasarframework quasar · Cross-site Scripting

Affects quasarframework quasarSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical : upgrade to 2.22.0 as a priority.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.22.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade quasar and quasarframework/quasar to 2.22.0.

Affected software

ProductAffectedFixed in
quasarframeworkquasarAffected
  • <2.22.0
Fixed in
  • 2.22.0
GitHubquasarframework/quasarpkg:github/quasarframework/quasarOther threatsAffected
  • <2.22.0
Fixed in
  • 2.22.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Quasar Framework version 2.22.0 or later, where this vulnerability is fixed. No other mitigations are indicated or required as the issue is resolved by proper encoding in the server-side rendering path. There is no indication that the vulnerability is mitigated by configuration or other means.

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.

References

Community reviews

Loading reviews…