JavaScript library with known vulnerabilities
Detects library versions from file names and banners and looks them up in OSV.dev.
Recommended next step if found
Update the library to the latest version, or remove it if the site no longer needs it.
Known library and runtime versions can provide useful security signals. Missing or blocked scripts limit what can be identified.
The following checks provide related public observations. Their presence does not mean this entire topic has been tested or that the application is secure.
Detects library versions from file names and banners and looks them up in OSV.dev.
Update the library to the latest version, or remove it if the site no longer needs it.
Compares the detected WordPress version with the latest release from api.wordpress.org.
Update WordPress to the latest version and enable automatic minor updates.
Detects PHP, nginx and Apache versions from headers and checks endoflife.date.
Upgrade to a supported release. Ask the hosting provider if you cannot change it yourself.
A blocked or unfinished check remains unverified. Review technical recommendations with the person operating the website and test changes before applying them to a live service.
Read the full methodology