How severe is GHSA-f8rq-m28h-8hxj?

No CVSS score has been assigned to GHSA-f8rq-m28h-8hxj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f8rq-m28h-8hxj?

GHSA-f8rq-m28h-8hxj affects the following packages: htmr (npm). Ecosystems affected: npm.

How do I fix GHSA-f8rq-m28h-8hxj?

Update htmr to 0.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f8rq-m28h-8hxj is resolved across your whole dependency graph.

How do I detect GHSA-f8rq-m28h-8hxj in my npm dependencies?

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

How do I mitigate GHSA-f8rq-m28h-8hxj 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-f8rq-m28h-8hxj actively exploited in the wild?

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

GHSA-f8rq-m28h-8hxj was published on September 3, 2020 and was last updated on August 31, 2020. 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 htmrGHSA-f8rq-m28h-8hxj

GHSA-f8rq-m28h-8hxj is a security vulnerability in htmr. A fix is available for htmr — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · 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.

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

htmrnpm

35Kdownloads / week

Description

Versions of htmr prior to 0.8.7 are vulnerable to Cross-Site Scripting (XSS). The package uses innerHTML to unescape HTML entities. This may lead to DOM-based XSS through HTML-encoded XSS payloads. This may allow an attacker to execute arbitrary JavaScript in a victim's browser.

Recommendation

Upgrade to version 0.8.7 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`htmr`	all versions	0.8.7`npm install htmr@0.8.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for htmr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update htmr to 0.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f8rq-m28h-8hxj is resolved across your whole dependency graph.
Workarounds
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

Versions of `htmr` prior to 0.8.7 are vulnerable to Cross-Site Scripting (XSS). The package uses `innerHTML` to unescape HTML entities. This may lead to [DOM-based XSS](https://owasp.org/www-community/attacks/DOM_Based_XSS) through HTML-encoded XSS payloads. This may allow an attacker to execute arbitrary JavaScript in a victim's browser. ## Recommendation Upgrade to version 0.8.7 or later.

O3 Security · Impact-Aware SCA

Is GHSA-f8rq-m28h-8hxj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works