Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-7jh9-6cpf-h4m7

CRITICAL

GHSA-7jh9-6cpf-h4m7 is a critical-severity (CVSS 9.9) Cross-site Scripting (XSS) vulnerability in hellojs. O3 Security confirms whether GHSA-7jh9-6cpf-h4m7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XSS in hello.js

Also known asCVE-2020-7741SNYK-JS-HELLOJS-1014546
Published
Jan 13, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

hellojsnpm
6Kdownloads / week

Description

This affects the package hello.js before 1.18.6. The code get the param oauth_redirect from url and pass it to location.assign without any check and sanitisation. So we can simply pass some XSS payloads into the url param oauth_redirect, such as javascript:alert(1).

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmhellojsall versions1.18.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update hellojs to 1.18.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7jh9-6cpf-h4m7 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7jh9-6cpf-h4m7 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-7jh9-6cpf-h4m7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects the package hello.js before 1.18.6. The code get the param oauth_redirect from url and pass it to location.assign without any check and sanitisation. So we can simply pass some XSS payloads into the url param oauth_redirect, such as `javascript:alert(1)`.
O3 Security · Impact-Aware SCA

Is GHSA-7jh9-6cpf-h4m7 in your dependencies?

O3 detects GHSA-7jh9-6cpf-h4m7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.