Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force should allow scanning of 403 sites #1592

Closed
ethicalhack3r opened this issue Jan 11, 2021 · 1 comment
Closed

Force should allow scanning of 403 sites #1592

ethicalhack3r opened this issue Jan 11, 2021 · 1 comment

Comments

@ethicalhack3r
Copy link
Contributor

When a site returns a 403 status code and the --force option is provided, WPScan will still refuse to scan the site, even though the user requested to force the scan.

wpscan --url https://redacted.com --force --random-user-agent                        
_______________________________________________________________
         __          _______   _____
         \ \        / /  __ \ / ____|
          \ \  /\  / /| |__) | (___   ___  __ _ _ __ ®
           \ \/  \/ / |  ___/ \___ \ / __|/ _` | '_ \
            \  /\  /  | |     ____) | (__| (_| | | | |
             \/  \/   |_|    |_____/ \___|\__,_|_| |_|

         WordPress Security Scanner by the WPScan Team
                         Version 3.8.7
       Sponsored by Automattic - https://automattic.com/
       @_WPScan_, @ethicalhack3r, @erwan_lr, @firefart
_______________________________________________________________


Scan Aborted: The target is responding with a 403, this might be due to a WAF. Well... --random-user-agent didn't work, you're on your own now!
@digininja
Copy link

Fully agree with this one!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants