# GHSA-j6v9-xgvh-f796: Command Injection in wxchangba

> Attackers can execute arbitrary system commands via unvalidated input in the wxchangba npm package, requiring immediate replacement of the module.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2020

## What is GHSA-j6v9-xgvh-f796?

GHSA-j6v9-xgvh-f796 is a command injection vulnerability in wxchangba, published on 11 Sep 2020. It can be exploited over the network, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-j6v9-xgvh-f796?

2 open source packages ship an affected version, including wxchangba.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wxchangba` | npm | From 0.0.0 | None |
| `wxchangba` | npm | From 0.0.0 | None |

## How do I fix GHSA-j6v9-xgvh-f796?

No fix has been published for GHSA-j6v9-xgvh-f796 yet. Limit exposure of the affected software until one is available.

## Is GHSA-j6v9-xgvh-f796 being exploited?

There is no known exploitation of GHSA-j6v9-xgvh-f796 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-j6v9-xgvh-f796 and fix it if it is affected.

What it is: GHSA-j6v9-xgvh-f796 is a command injection vulnerability in wxchangba, published on 11 Sep 2020. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-j6v9-xgvh-f796 in the wild and no public exploit code.

Affected packages and fixed versions:
- wxchangba (npm): affected from 0.0.0; no fix listed
- wxchangba (npm): affected from 0.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-j6v9-xgvh-f796/ (Markdown: https://insights.sbomify.com/GHSA-j6v9-xgvh-f796/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-j6v9-xgvh-f796

---
From sbomify Insights: https://insights.sbomify.com/GHSA-j6v9-xgvh-f796/
Summaries are generated and may contain mistakes; the official description above is the record.