How severe is GHSA-ccrp-c664-8p4j?

No CVSS score has been assigned to GHSA-ccrp-c664-8p4j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ccrp-c664-8p4j?

GHSA-ccrp-c664-8p4j affects the following packages: markdown-to-jsx (npm). Ecosystems affected: npm.

How do I fix GHSA-ccrp-c664-8p4j?

Update markdown-to-jsx to 6.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ccrp-c664-8p4j is resolved across your whole dependency graph.

How do I detect GHSA-ccrp-c664-8p4j in my npm dependencies?

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

How do I mitigate GHSA-ccrp-c664-8p4j if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-ccrp-c664-8p4j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ccrp-c664-8p4j can be triaged on real exposure rather than presence alone.

Is GHSA-ccrp-c664-8p4j actively exploited in the wild?

No public exploit code has been indexed for GHSA-ccrp-c664-8p4j 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-ccrp-c664-8p4j published, and has it been updated?

GHSA-ccrp-c664-8p4j was published on September 3, 2020 and was last updated on September 29, 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

GHSA-ccrp-c664-8p4j — markdown-to-jsx

Fix: probablyup/markdown-to-jsx#307

GHSA-ccrp-c664-8p4j is a security vulnerability in markdown-to-jsx. A fix is available for markdown-to-jsx — see the affected versions and patch details below.

Cross-Site Scripting in markdown-to-jsx

Published

Sep 3, 2020

Updated

Sep 29, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 29, 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.

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

markdown-to-jsxnpm

3.8Mdownloads / week

Description

Versions of markdown-to-jsx prior to 6.11.4 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization the package may render output containing malicious JavaScript. This vulnerability can be exploited through input of links containing data or VBScript URIs and a base64-encoded payload.

Recommendation

Upgrade to version 6.11.4 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`markdown-to-jsx`	all versions	6.11.4`npm install markdown-to-jsx@6.11.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for markdown-to-jsx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update markdown-to-jsx to 6.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ccrp-c664-8p4j is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ccrp-c664-8p4j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-ccrp-c664-8p4j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `markdown-to-jsx` prior to 6.11.4 are vulnerable to Cross-Site Scripting. Due to insufficient input sanitization the package may render output containing malicious JavaScript. This vulnerability can be exploited through input of links containing `data` or VBScript URIs and a base64-encoded payload. ## Recommendation Upgrade to version 6.11.4 or later.

O3 Security · Impact-Aware SCA

Is GHSA-ccrp-c664-8p4j in your dependencies?

O3 Security finds GHSA-ccrp-c664-8p4j across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works