CVE-2022-25916 is a high-severity (CVSS 7.4) OS Command Injection vulnerability in mt7688-wiscan. A fix is available for mt7688-wiscan — see the affected versions and patch details below.
mt7688-wiscan is vulnerable to Command Injection due to improper input sanitization
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-25916.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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.
mt7688-wiscannpmDescription
Versions of the package mt7688-wiscan before 0.8.3 are vulnerable to Command Injection due to improper input sanitization in the 'wiscan.scan' function.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | mt7688-wiscan | all versions | 0.8.3npm install mt7688-wiscan@0.8.3 |
Affected Products
mt7688-wiscanmt7688-wiscan_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mt7688-wiscan, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mt7688-wiscan to 0.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25916 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
Is CVE-2022-25916 in your dependencies?
Find it across npm, including transitive dependencies.