How severe is GHSA-9cw2-jqp5-7x39?

GHSA-9cw2-jqp5-7x39 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-9cw2-jqp5-7x39?

GHSA-9cw2-jqp5-7x39 affects the following packages: marked (npm). Ecosystems affected: npm.

How do I fix GHSA-9cw2-jqp5-7x39?

Update marked to 0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9cw2-jqp5-7x39 is resolved across your whole dependency graph.

How do I detect GHSA-9cw2-jqp5-7x39 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for marked. 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.

How do I mitigate GHSA-9cw2-jqp5-7x39 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-9cw2-jqp5-7x39?

O3 pinpoints whether GHSA-9cw2-jqp5-7x39 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9cw2-jqp5-7x39 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9cw2-jqp5-7x39 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.

What type of vulnerability is GHSA-9cw2-jqp5-7x39?

GHSA-9cw2-jqp5-7x39 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-9cw2-jqp5-7x39 published, and has it been updated?

GHSA-9cw2-jqp5-7x39 was published on August 31, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-9cw2-jqp5-7x39

MEDIUM

GHSA-9cw2-jqp5-7x39 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in marked. O3 Security confirms whether GHSA-9cw2-jqp5-7x39 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Multiple Content Injection Vulnerabilities in marked

Also known asCVE-2014-3743

Published

Aug 31, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

markednpm

61.4Mdownloads / week

Description

Versions 0.3.0 and earlier of marked are affected by two cross-site scripting vulnerabilities, even when sanitize: true is set.

The attack vectors for this vulnerability are GFM Codeblocks and JavaScript URLs.

Recommendation

Upgrade to version 0.3.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`marked`	all versions	0.3.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for marked. 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.
Fix
Update marked to 0.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9cw2-jqp5-7x39 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 pinpoints whether GHSA-9cw2-jqp5-7x39 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-9cw2-jqp5-7x39. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions 0.3.0 and earlier of `marked` are affected by two cross-site scripting vulnerabilities, even when `sanitize: true` is set. The attack vectors for this vulnerability are GFM Codeblocks and JavaScript URLs. ## Recommendation Upgrade to version 0.3.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-9cw2-jqp5-7x39 in your dependencies?

O3 detects GHSA-9cw2-jqp5-7x39 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works