How severe is GHSA-xr53-m937-jr9c?

No CVSS score has been assigned to GHSA-xr53-m937-jr9c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xr53-m937-jr9c?

GHSA-xr53-m937-jr9c affects the following packages: ngx-md (npm). Ecosystems affected: npm.

How do I fix GHSA-xr53-m937-jr9c?

Update ngx-md to 6.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr53-m937-jr9c is resolved across your whole dependency graph.

How do I detect GHSA-xr53-m937-jr9c in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ngx-md. 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-xr53-m937-jr9c 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-xr53-m937-jr9c?

O3 pinpoints whether GHSA-xr53-m937-jr9c 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-xr53-m937-jr9c actively exploited in the wild?

No public exploit code has been indexed for GHSA-xr53-m937-jr9c 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-xr53-m937-jr9c published, and has it been updated?

GHSA-xr53-m937-jr9c was published on September 3, 2020 and was last updated on October 4, 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-xr53-m937-jr9c

GHSA-xr53-m937-jr9c is a remote code execution vulnerability in ngx-md. O3 Security confirms whether GHSA-xr53-m937-jr9c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in ngx-md

Published

Sep 3, 2020

Updated

Oct 4, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 4, 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

ngx-mdnpm

1Kdownloads / week

Description

Versions of ngx-md prior to 6.0.3 are vulnerable to Cross-Site Scripting. Links are not properly restricted to http/https and can contain JavaScript which may lead to arbitrary code execution. Markdown input such as [Click Me](javascript:alert('Injected!'%29) is rendered as a Click Me link that executes JavaScript.

Recommendation

Upgrade to version 6.0.3 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ngx-md`	all versions	6.0.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ngx-md. 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 ngx-md to 6.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr53-m937-jr9c 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-xr53-m937-jr9c 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-xr53-m937-jr9c. 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 `ngx-md` prior to 6.0.3 are vulnerable to Cross-Site Scripting. Links are not properly restricted to http/https and can contain JavaScript which may lead to arbitrary code execution. Markdown input such as `[Click Me](javascript:alert('Injected!'%29)` is rendered as a `Click Me` link that executes JavaScript. ## Recommendation Upgrade to version 6.0.3 or later.

O3 Security · Impact-Aware SCA

Is GHSA-xr53-m937-jr9c in your dependencies?

O3 detects GHSA-xr53-m937-jr9c 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