How severe is GHSA-4x6x-782q-jfc4?

No CVSS score has been assigned to GHSA-4x6x-782q-jfc4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4x6x-782q-jfc4?

GHSA-4x6x-782q-jfc4 affects the following packages: node-wifi (npm). Ecosystems affected: npm.

How do I fix GHSA-4x6x-782q-jfc4?

Update node-wifi to 2.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4x6x-782q-jfc4 is resolved across your whole dependency graph.

How do I detect GHSA-4x6x-782q-jfc4 in my npm dependencies?

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

How do I mitigate GHSA-4x6x-782q-jfc4 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-4x6x-782q-jfc4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4x6x-782q-jfc4 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-4x6x-782q-jfc4 published, and has it been updated?

GHSA-4x6x-782q-jfc4 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

Command Injection in node-wifiGHSA-4x6x-782q-jfc4

GHSA-4x6x-782q-jfc4 is a remote code execution vulnerability in node-wifi. A fix is available for node-wifi — 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.

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

node-wifinpm

7Kdownloads / week

Description

Versions of node-wifi prior to 2.0.12 are vulnerable to Command Injection. The package fails to sanitize user input, allowing attackers to inject commands through the ssid variable and possibly achieving Remote Code Execution on the system.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-wifi`	all versions	2.0.12`npm install node-wifi@2.0.12`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-wifi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update node-wifi to 2.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4x6x-782q-jfc4 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

Versions of `node-wifi` prior to 2.0.12 are vulnerable to Command Injection. The package fails to sanitize user input, allowing attackers to inject commands through the `ssid` variable and possibly achieving Remote Code Execution on the system. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-4x6x-782q-jfc4 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works