NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2025-43954 — @quasar/quasar-ui-qmarkdo…

MEDIUMFix: quasarframework/quasar-ui-qmarkdown@b61dff8

CVE-2025-43954 is a medium-severity (CVSS 4.9) Cross-site Scripting (XSS) vulnerability in @quasar/quasar-ui-qmarkdown. A fix is available for @quasar/quasar-ui-qmarkdown — see the affected versions and patch details below.

QMarkdown Cross-Site Scripting (XSS) vulnerability

Also known asGHSA-wm65-ph3w-587c
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-43954.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk+0.00%
Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk
0.00%0.24%0.48%0.71%0.1%0.2%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@quasar/quasar-ui-qmarkdownnpm
9Kdownloads / week

Description

QMarkdown (aka quasar-ui-qmarkdown) before 2.0.5 allows XSS via headers even when when no-html is set.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@quasar/quasar-ui-qmarkdownall versions2.0.5npm install @quasar/quasar-ui-qmarkdown@2.0.5

Affected Products

1 product · 1 configurations
Application
qmarkdownquasar
< 2.0.5
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @quasar/quasar-ui-qmarkdown, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @quasar/quasar-ui-qmarkdown to 2.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-43954 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

QMarkdown (aka quasar-ui-qmarkdown) before 2.0.5 allows XSS via headers even when when no-html is set.
O3 Security · Impact-Aware SCA

Is CVE-2025-43954 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-43954: @quasar/quasar-ui XSS — Fixed in 2.0.5