vitejs vite up to 5.4.19/6.3.5/7.0.6/7.1.4 path traversal

Summaryinfo

A vulnerability was found in vitejs vite up to 5.4.19/6.3.5/7.0.6/7.1.4. It has been classified as problematic. The affected element is an unknown function. The manipulation leads to path traversal. This vulnerability is listed as CVE-2025-58752. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in vitejs vite up to 5.4.19/6.3.5/7.0.6/7.1.4. It has been rated as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-23. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. Impacted is confidentiality. The summary by CVE is:

Vite is a frontend tooling framework for JavaScript. Prior to versions 7.1.5, 7.0.7, 6.3.6, and 5.4.20, any HTML files on the machine were served regardless of the `server.fs` settings. Only apps that explicitly expose the Vite dev server to the network (using --host or server.host config option) and use `appType: 'spa'` (default) or `appType: 'mpa'` are affected. This vulnerability also affects the preview server. The preview server allowed HTML files not under the output directory to be served. Versions 7.1.5, 7.0.7, 6.3.6, and 5.4.20 fix the issue.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-58752 since 09/04/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 5.4.20, 6.3.6, 7.0.7 or 7.1.5 eliminates this vulnerability. Applying the patch 0ab19ea9fcb66f544328f442cf6e70f7c0528d5f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• vitejs

Name

• vite

Version

• 5.4.0
• 5.4.1
• 5.4.2
• 5.4.3
• 5.4.4
• 5.4.5
• 5.4.6
• 5.4.7
• 5.4.8
• 5.4.9
• 5.4.10
• 5.4.11
• 5.4.12
• 5.4.13
• 5.4.14
• 5.4.15
• 5.4.16
• 5.4.17
• 5.4.18
• 5.4.19
• 6.3.0
• 6.3.1
• 6.3.2
• 6.3.3
• 6.3.4
• 6.3.5
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.1.0
• 7.1.1
• 7.1.2
• 7.1.3
• 7.1.4

License

• open-source

Website

• Product: https://github.com/vitejs/vite/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion