wpscan version 3.4.0

We're tracking this issue on the wpscan Github here: https://github.com/wpscanteam/wpscan/issues/1243

Looks like a loop...

wpscan team asks to create a kali bug tracker...and kali team says its wpscan devs to resolve the issue... :)

my bad... please ignore the previous note

Where is /usr/local/bin/wpscan from? Because the Kali package installs it to /usr/bin/wpscan

@sumgro, if you mixup manual installation via "gem" and installation via .deb, you will surely end up in problems like the one shown here. Please don't do that. Can you reproduce the problem with a fresh Kali install or on the daily live image? https://archive.kali.org/kali-daily-images/

As steev pointed out, /usr/local/bin/wpscan is not provided by any Kali package. It's your fault if you manually installed wpscan and if it doesn't get properly updated... some of the dependencies might be managed by apt and they will get out of sync with whatever you installed manually. We ensure consistency between all Debian packages, we can't ensure consistency with whatever you installed manually.

@rhertzog I get it, let me try that and come back. Thanks

Update: Resolved by following the below steps:

Remove wpscan installed manually through gem - gem uninstall wpscan
Install wpscan via Kali repository - apt get wpscan

wpscan now works.

@sumgro solved his problem as explained here:
https://github.com/wpscanteam/wpscan/issues/1243#issuecomment-441670644

He just did this to fix his problem:

gem uninstall wpscan

apt install wpscan

Thus confirming our diagnosis.