Random example: 1 vulnerable library detected:
https://retire.insecurity.today/#!/scan/34521ce556e65d3c51898f915d34963da9b6abaa77d57f8d11d6797ac369ffcaDOM-XSS issues: Results from scanning URL: -http://www.camillesanz.com/wp-includes/js/imagesloaded.min.js?ver=3.2.0
Number of sources found: 41
Number of sinks found: 17
&
Results from scanning URL: -http://www.camillesanz.com/wp-includes/js/imagesloaded.min.js?ver=3.2.0
Number of sources found: 41
Number of sinks found: 17
&
Results from scanning URL: -https://stats.wp.com/e-201943.js
Number of sources found: 2
Number of sinks found: 4
Wrong settings: User Enumeration
The first two user ID's were tested to determine if user enumeration is possible.
ID User Login
1 None None
2 fraizsz fraizsz
It is recommended to rename the admin user account to reduce the chance of brute force attacks occurring. As this will reduce the chance of automated password attackers gaining access. However it is important to understand that if the author archives are enabled it is usually possible to enumerate all users within a WordPress installation.
&
Directory Indexing
In the test an attempt was made to list the directory contents of the uploads and plugins folders to determine if Directory Indexing is enabled. This is a common information leakage vulnerability that can reveal sensitive information regarding your site configuration or content.
/wp-content/uploads/ enabled
/wp-content/plugins/ disabled
Directory indexing was tested on the /wp-content/uploads/ and /wp-content/plugins/ directores. Note that other directories may have this web server feature enabled, so ensure you check other folders in your installation. It is good practice to ensure directory indexing is disabled for your full WordPress installation either through the web server configuration or .htaccess.
378 Website improvement recommendations found through linting:
https://webhint.io/scanner/0883b126-3d63-4297-ad65-289f4d5e962epolonus (volunteer 3rd party cold recon website security analyst and website error-hunter)
