CVE-2022-25926 json
window-control vulnerable to Command Injection due to improper input sanitization
published 3y ago modified 4mo ago also GHSA-9mjx-wfqp-j5ph , EUVD-2023-0433
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
Versions of the package window-control before 1.4.5 are vulnerable to Command Injection via the sendKeys function, due to improper input sanitization.
Patch / fix
- npm window-control 1.4.5
- n/a window-control 1.4.5
Is CVE-2022-25926 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P |
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | window-control | <1.4.5 |
1.4.5 |
Affected products
- n/a window-control
Classification
References
-
github.com
/bruno-robert/window-control/commit/075c854534a749d887655a906759f5a7eee95173
web, patch, third-party-advisory
-
security.snyk.io
/vuln/SNYK-JS-WINDOWCONTROL-3186345
web, third-party-advisory
-
github.com
/bruno-robert/window-control/releases/tag/v1.4.5
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-25926
advisory
-
github.com
/bruno-robert/window-control
package
Sources
- CVE List CVE-2022-25926
- GitHub Advisory GHSA-9mjx-wfqp-j5ph
- NVD CVE-2022-25926
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.