Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-m7qm-r2r5-f77q

GHSA-m7qm-r2r5-f77q is a security vulnerability in react-marked-markdown. O3 Security confirms whether GHSA-m7qm-r2r5-f77q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in react-marked-markdown

Published
Sep 1, 2020
Updated
Sep 24, 2021
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Sep 24, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
📦react-marked-markdown

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

All versions of react-marked-markdown are vulnerable to cross-site scripting (XSS) via href attributes. This is exploitable if user is provided to react-marked-markdown

Proof of concept:

import React from 'react'
import ReactDOM from 'react-dom'
import { MarkdownPreview } from 'react-marked-markdown'

ReactDOM.render(
<MarkdownPreview
markedOptions={{ sanitize: true }}
value={'[XSS](javascript: alert`1`)'}
/>,
document.getElementById('root')
)

Recommendation

No fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time if you allow user input into href values.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmreact-marked-markdown0.0.0No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-marked-markdown. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of react-marked-markdown has shipped for GHSA-m7qm-r2r5-f77q yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-m7qm-r2r5-f77q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m7qm-r2r5-f77q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

All versions of `react-marked-markdown` are vulnerable to cross-site scripting (XSS) via `href` attributes. This is exploitable if user is provided to `react-marked-markdown` Proof of concept: ``` import React from 'react' import ReactDOM from 'react-dom' import { MarkdownPreview } from 'react-marked-markdown' ReactDOM.render( <MarkdownPreview markedOptions={{ sanitize: true }} value={'[XSS](javascript: alert`1`)'} />, document.getElementById('root') ) ``` ## Recommendation No fix is currently available for this vulnerability. It is our recommendation to not install or use this module at
O3 Security · Impact-Aware SCA

Is GHSA-m7qm-r2r5-f77q in your dependencies?

O3 detects GHSA-m7qm-r2r5-f77q across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-m7qm-r2r5-f77q: Cross-Site Scripting… | O3 Security