How severe is GHSA-wgw3-gf4p-62xc?

No CVSS score has been assigned to GHSA-wgw3-gf4p-62xc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wgw3-gf4p-62xc?

GHSA-wgw3-gf4p-62xc affects the following packages: wizard-syncronizer (npm). Ecosystems affected: npm.

How do I fix GHSA-wgw3-gf4p-62xc?

No patched version of wizard-syncronizer has shipped for GHSA-wgw3-gf4p-62xc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-wgw3-gf4p-62xc in my npm dependencies?

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

How do I mitigate GHSA-wgw3-gf4p-62xc 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-wgw3-gf4p-62xc actively exploited in the wild?

No public exploit code has been indexed for GHSA-wgw3-gf4p-62xc 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-wgw3-gf4p-62xc published, and has it been updated?

GHSA-wgw3-gf4p-62xc was published on September 11, 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 wizard-syncronizerGHSA-wgw3-gf4p-62xc

GHSA-wgw3-gf4p-62xc is a remote code execution vulnerability in wizard-syncronizer. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 11, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

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.

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

wizard-syncronizernpm

7downloads / week

Description

All versions of wizard-syncronizer are vulnerable to Command Injection. The package does not validate input on the cloneAndSync function and concatenates it to an exec call. This can be abused through a malicious widget containing the payload in the gitURL value or through a MITM attack since the package does not enforce HTTPS. This may allow attackers to run arbitrary commands in the system.

Recommendation

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

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`wizard-syncronizer`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wizard-syncronizer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of wizard-syncronizer has shipped for GHSA-wgw3-gf4p-62xc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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

All versions of `wizard-syncronizer` are vulnerable to Command Injection. The package does not validate input on the `cloneAndSync` function and concatenates it to an exec call. This can be abused through a malicious widget containing the payload in the `gitURL` value or through a MITM attack since the package does not enforce HTTPS. This may allow attackers to run arbitrary commands in the system. ## Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-wgw3-gf4p-62xc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works