How severe is GHSA-m7qm-r2r5-f77q?

No CVSS score has been assigned to GHSA-m7qm-r2r5-f77q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m7qm-r2r5-f77q?

GHSA-m7qm-r2r5-f77q affects the following packages: react-marked-markdown (npm). Ecosystems affected: npm.

How do I fix GHSA-m7qm-r2r5-f77q?

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.

How do I detect GHSA-m7qm-r2r5-f77q in my npm dependencies?

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

How do I mitigate GHSA-m7qm-r2r5-f77q if there is no patch (or I can't update yet)?

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.

Is GHSA-m7qm-r2r5-f77q actively exploited in the wild?

No public exploit code has been indexed for GHSA-m7qm-r2r5-f77q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-m7qm-r2r5-f77q published, and has it been updated?

GHSA-m7qm-r2r5-f77q was published on September 1, 2020 and was last updated on September 24, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Cross-Site Scripting in react-marked-markdownGHSA-m7qm-r2r5-f77q

GHSA-m7qm-r2r5-f77q is a security vulnerability in react-marked-markdown. No vendor fix is recorded yet; mitigation options are listed below.

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

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.

11other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

react-marked-markdownnpm

415downloads / week

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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`react-marked-markdown`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-marked-markdown, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.
Mitigate without a patch
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

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works