search

wpscanteam / wpscan

WPScan WordPress security scanner. Written for security professionals and blog maintainers to test the security of their WordPress websites. Contact us via contact@wpscan.com
https://wpscan.com/wordpress-cli-scanner
Other
8.62k stars 1.27k forks source link

bruteforce retries #800

Open Viss opened 9 years ago

Viss commented 9 years ago

sometimes to evade mod_security, I use a bunch of different proxies and I've configured a load balancer to rotate them. Sometimes the proxies barf, or wpscan tries to hit a proxy during the rotation and gets an unexpected result back from the upstream connection. It would be pretty awesome to have a 'retries' functionality available so that it can validate whether the attempt actually succeeded or actually failed by trying for either a valid positive or valid negative response from the wordpress install, rather than a proxy error or a timeout.

ethicalhack3r commented 9 years ago

Hi @Viss!

Thanks for the feedback. We're currently in a situation where we're re-writing WPScan to make it more easily maintainable, extendable and support stuff like machine readable output.

In this re-written version, we are heavily considering dropping the brute force feature. Mainly due to issues like this and other 'advanced' brute forcing features that we lack. We think that maybe tools dedicated to remote password brute forcing would be better for our users to use.

That being said, it is easier for users to brute force WP within the same WP testing tool. We're not sure whether the effort of implementing the feature will be worth it as it will take some effort to make this feature fit into the new version.

Very happy to receive people's thoughts on this though!

Viss commented 9 years ago

aw, thats unfortunate - I quite like the bruteforce capability. It's easier to point wpscan at a wp target than to knock out a giant hydra command line, that's for sure!

lnxg33k commented 9 years ago

Guys don't drop the brute-force feature, most of people use it all the time and it is amazing, you can just add tampering engine, something like sqlmap but on the whole layer as that may solve problems like @Viss one.

ethicalhack3r commented 9 years ago

@lnxg33k brute force feature won't be dropped anymore, it has already been implemented in v3 which is still in private :)

This feature isn't in v3 as far as I'm aware and not sure how easy it would be to implement. Maybe @erwanlr can comment as he is the one who has been working on v3 :)

rafael1138 commented 7 years ago

Do you know when the new version is going to be live?