vite-plus vulnerabilities
The Unified Toolchain for the Web
- Registry
- npm
- Latest
- 1.4.0
- License
- MIT
11 known advisories
The latest version, 1.4.0, is not affected by any of them. Projects on older versions may be.
npm install vite-plus@1.4.0Security advisories for vite-plus
Vitest: Servers misapply `server.fs.deny`, serving `.env`, private keys, `.git`, and the API token file
- Affected
- >=1.0.0-rc.0 <1.3.0
- Fixed in
- 1.3.0
Vite: Cross origin script execution through Vite custom middleware
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Vite: First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance`
- Affected
- >=0.2.8 <1.1.0
- Fixed in
- 1.1.0
launch-editor: Editor CLI flag misinterpretation causing arbitrary command execution for some editors
- Affected
- <1.1.0
- Fixed in
- 1.1.0
launch-editor: `fs.existsSync()` existence check can be bypassed on Windows
- Affected
- <1.1.0
- Fixed in
- 1.1.0
launch-editor: escapeCmdArgs() omits % escaping on Windows
- Affected
- <1.1.0
- Fixed in
- 1.1.0
Vitest Browser: Exposed Browser Mode API Can Proxy CDP and Overwrite Config Files, Leading to RCE
- Affected
- <0.1.24
- Fixed in
- 0.1.24
launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows
- Affected
- <0.1.24
- Fixed in
- 0.1.24
vite: `server.fs.deny` bypass on Windows alternate paths
- Affected
- <0.1.24
- Fixed in
- 0.1.24
Path traversal in vite-plus/binding downloadPackageManager() writes outside VP_HOME
- Affected
- <0.1.17
- Fixed in
- 0.1.17
Which of your client projects still run an old vite-plus?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.