wpscan VS vane

After our initial port scan, we might do more scans depending on what we find. In order to be as effective as possible, and to gather as much information as possible, pentesters are often running multiple scans simultaneously on a target. There are hundreds of tools out there for every service imaginable. Some of the tools worth mentioning are wpscan (https://wpscan.com/wordpress-security-scanner) for Wordpress sites or sqlmap (https://sqlmap.org/) for automatic SQL injection. For a more extensive list of tools check out https://0xcybery.github.io/ehtk/ or https://github.com/enaqx/awesome-pentest

So the website is using Wordpress. Having said that, we are going to use WPScan. But before that, make sure that you have already acquired your API token before using WPScan or you will never be able to utilize the scanner. You can get your own API token by signing up on their website.

Specialised tools can be used, for example WPScan. Allowing us to enumerate the wordpress CMS.

Linux Servers (Remotely): nmap -> nmap -sC -sV -p- ipHere WordPress Websites: wpscan -> wpscan --url http://site.com/

There is one annoying "gotcha" when using WPScan, especially plugin enumeration, which is for the best results you have to go an extra step and add the "--plugins-detection mixed" option. It is documented in our user documentation - https://github.com/wpscanteam/wpscan/wiki/WPScan-User-Documentation#enumeration-modes

There is a free wordpress security scanning service that you could leverage for regular security auditing of your site called WPScan that is fantastic on detecting and auditing common vulnerabilities to plugins and security exposures.

wpscan will audit for plugins used that have publicly exposed vulnerabilities. The methods of detection are quite clever and it works well.

Is there an active fork? This looks dead https://github.com/delvelabs/vane