• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question How to Detect and Mitigate Next.js / React Vulnerabilities on Windows Plesk Server

teletek

New Pleskian
Server operating system version
Windows Server 2019
Plesk version and microupdate number
Plesk Obsidian 18.0.70 Update #4
Hello Plesk Community,


I am running a Plesk server on Windows OS and hosting a web application built with Next.js / React. I would like guidance on how to properly detect, verify, and mitigate potential security vulnerabilities related to these frameworks.


Specifically, I would appreciate help with the following points:




1. How can I detect if my application is affected by a Next.js / React vulnerability?​


  • Are there recommended tools or commands to scan for known vulnerabilities (e.g. CVEs)?
  • Can this be done directly from the Plesk interface or via command line on Windows?
  • Are there Plesk extensions or security scanners that can help identify vulnerable JavaScript dependencies?



2. How can I check the installed Next.js and React versions?​


On a Windows Plesk server:


  • Which files should I check to confirm the exact versions (e.g. package.json, package-lock.json, node_modules)?
  • Are there recommended Node.js or npm commands to safely retrieve version information in a production environment?

Example:


  • npm list next
  • npm list react

Is this the correct and safe approach on a live Plesk-hosted site?




3. How should I update Next.js / React securely?​


  • What is the recommended upgrade path for Next.js and React on a Windows server?
  • Should the update be performed locally and then redeployed, or directly on the server?
  • Are there best practices to avoid downtime when updating JavaScript frameworks on Plesk?



4. Plesk & Windows-specific considerations​


  • Are there any Windows-specific limitations or known issues when running Next.js applications on Plesk?
  • Does Plesk provide official guidance for securing Node.js applications against known vulnerabilities?



5. Logging and monitoring​


  • Where can I find logs related to Node.js / Next.js execution in Plesk on Windows?
  • How can I monitor suspicious behavior that may indicate exploitation attempts?



Any best practices, documentation links, or real-world experiences would be greatly appreciated.


Thank you in advance for your support.


Best regards,
 
Back
Top