Find vulnerable JavaScript libraries loaded by your website
A website can still load an old copy of a library after the app around it has changed. A known vulnerability finding links an identified library version to a published advisory.
SiteCMD runs this check after you prove the site is yours, starting with the first scan after proof.
Update jQuery and other vulnerable libraries without breaking your pages
- 1
Locate the affected file and version
Identify the script in the live page, such as a jQuery or Bootstrap file, and the version it contains. Include files copied directly into the project or loaded from a CDN, as well as packages installed by a package manager.
- 2
Read the advisory before choosing a replacement
Check the affected versions and the conditions described by the advisory. Choose a maintained release that addresses the issue and review its migration guidance.
- 3
Test the parts of the page that use the library
Try the affected controls and interactions after updating. Replace old integration code where the new release requires it, then confirm the deployed page loads the intended file.
Find copied library files with Retire.js
A library copied into a public folder may not appear in a package manifest. Retire.js is one tool that can identify JavaScript library versions with known vulnerabilities, including copied files.
A package file lists what the project installs, which may differ from the file a live page loads.
Frequently asked questions
Does a vulnerable jQuery version mean my site was hacked?
No. Use the advisory to investigate the affected code and its conditions. Finding a vulnerable version calls for review; it isn't evidence that an attack has happened.
Check integrity alongside JavaScript library versions
Website security
Catch leaked API keys and exposed files before someone uses them against you.
Subresource Integrity
Use integrity hashes to tie an outside script or stylesheet to the contents you reviewed.