Nuxt MDC has an XSS vulnerability in markdown rendering that bypasses HTML filtering
CVE-2025-54075GHSA-cj6r-rrr9-fg82
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nuxtjs/mdc 0.17.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @nuxtjs/mdc
- Affected
- < 0.17.2
- Fixed in
- 0.17.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-cj6r-rrr9-fg82 lists affected ranges: npm @nuxtjs/mdc >=0 <0.17.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-cj6r-rrr9-fg82 lists affected ranges: npm @nuxtjs/mdc >=0 <0.17.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
- EPSS
- CVE-2025-54075: 0.34% estimated exploitation activity in the next 30 days; percentile 28.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary A remote script-inclusion / stored XSS vulnerability in @nuxtjs/mdc lets a Markdown author inject a <base href="https://attacker.tld" element. The <base tag rewrites how all subsequent relative URLs are resolved, so an attacker can make the page load scripts, styles, or images from an external, attacker-controlled origin and execute arbitrary JavaScript in the site’s context. Details - Affected file : src/runtime/parser/utils/props.ts - Core logic : validateProp() inspects attributes that start with on → blocked href or src → filtered by isAnchorLinkAllowed() Every other attribute and every tag (including <base) is allowed unchanged, so the malicious href on <base is never validated. As soon as <base href="https://vozec.fr" is parsed, any later relative path—/script.js, ../img.png, etc.—is fetched from the attacker’s domain. Proof of Concept Place the following in any Markdown handled by Nuxt MDC: 1. Start the Nuxt app (npm run dev). 2. Visit the page. 3. The browser requests…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-cj6r-rrr9-fg82
- Revision 1 · created ·
Published from osv record GHSA-cj6r-rrr9-fg82
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-54075 Advisory: Nuxt MDC has an XSS vulnerability in markdown rendering that bypasses HTML filtering IDs: CVE-2025-54075, GHSA-cj6r-rrr9-fg82 Record: https://patchnext.com/advisories/cve-2025-54075 (revision 2, source checked 26 Oct 2026, 12:37 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @nuxtjs/mdc 0.17.2. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @nuxtjs/mdc: affected < 0.17.2; fixed in 0.17.2 ## Suggested inspection (read-only) - `npm ls @nuxtjs/mdc --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @nuxtjs/mdc. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-cj6r-rrr9-fg82 (OSV record GHSA-cj6r-rrr9-fg82 lists affected ranges: npm @nuxtjs/mdc >=0 <0.17.2 (fixed)) - Verified: https://github.com/advisories/GHSA-cj6r-rrr9-fg82 (GitHub-reviewed advisory GHSA-cj6r-rrr9-fg82 lists affected ranges: npm @nuxtjs/mdc >=0 <0.17.2) Commands are suggestions: review each one before running it.
Loading voting…