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

GHSA-j6v9-xgvh-f796

GHSA-j6v9-xgvh-f796 is a remote code execution vulnerability in wxchangba. O3 Security confirms whether GHSA-j6v9-xgvh-f796 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Command Injection in wxchangba

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
wxchangbanpm
4downloads / week

Description

All versions of wxchangba are vulnerable to Command Injection. The package does not validate user input on the reqPostMaterial function, passing contents of the file parameter to an exec call. 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
EcosystemPackageVulnerable rangeFix
📦npmwxchangba0.0.0No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

    No patched version of wxchangba has shipped for GHSA-j6v9-xgvh-f796 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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-j6v9-xgvh-f796 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-j6v9-xgvh-f796. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

All versions of `wxchangba` are vulnerable to Command Injection. The package does not validate user input on the `reqPostMaterial` function, passing contents of the `file` parameter to an exec call. 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-j6v9-xgvh-f796 in your dependencies?

O3 detects GHSA-j6v9-xgvh-f796 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-j6v9-xgvh-f796: Command Injection in… | O3 Security