How severe is GHSA-hpr5-wp7c-hh5q?

No CVSS score has been assigned to GHSA-hpr5-wp7c-hh5q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hpr5-wp7c-hh5q?

GHSA-hpr5-wp7c-hh5q affects the following packages: mrk.js (npm). Ecosystems affected: npm.

How do I fix GHSA-hpr5-wp7c-hh5q?

Update mrk.js to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hpr5-wp7c-hh5q is resolved across your whole dependency graph.

How do I detect GHSA-hpr5-wp7c-hh5q in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mrk.js. 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-hpr5-wp7c-hh5q 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-hpr5-wp7c-hh5q?

O3 pinpoints whether GHSA-hpr5-wp7c-hh5q 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-hpr5-wp7c-hh5q actively exploited in the wild?

No public exploit code has been indexed for GHSA-hpr5-wp7c-hh5q 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-hpr5-wp7c-hh5q published, and has it been updated?

GHSA-hpr5-wp7c-hh5q was published on September 1, 2020 and was last updated on September 23, 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-hpr5-wp7c-hh5q

Fix: heyitsmeuralex/mrk#3

GHSA-hpr5-wp7c-hh5q is a security vulnerability in mrk.js. O3 Security confirms whether GHSA-hpr5-wp7c-hh5q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in mrk.js

Published

Sep 1, 2020

Updated

Sep 23, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 23, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦mrk.js

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

Versions of mrk.js before 2.0.1 are vulnerable to cross-site scripting (XSS) when markdown is converted to HTML.

Recommendation

Update to version 2.0.1 or later and use mark.sanitizeURL() for any src and href attributes when extending the markdown.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mrk.js`	all versions	2.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mrk.js. 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 mrk.js to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hpr5-wp7c-hh5q 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-hpr5-wp7c-hh5q 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-hpr5-wp7c-hh5q. 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 `mrk.js` before 2.0.1 are vulnerable to cross-site scripting (XSS) when markdown is converted to HTML. ## Recommendation Update to version 2.0.1 or later and use `mark.sanitizeURL()` for any `src` and `href` attributes when extending the markdown.

O3 Security · Impact-Aware SCA

Is GHSA-hpr5-wp7c-hh5q in your dependencies?

O3 detects GHSA-hpr5-wp7c-hh5q 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