From 31f70a9762921ccfe4a3bda9459dad26e95f4351 Mon Sep 17 00:00:00 2001 From: Ryan Dewhurst Date: Wed, 6 Jan 2021 15:14:53 +0100 Subject: [PATCH] Updated WPScan User Documentation (markdown) --- WPScan-User-Documentation.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/WPScan-User-Documentation.md b/WPScan-User-Documentation.md index eeeaddb..dec9d16 100644 --- a/WPScan-User-Documentation.md +++ b/WPScan-User-Documentation.md @@ -128,6 +128,10 @@ _NOTE: Get your API token from [wpscan.com](https://wpscan.com/) if you also wan `wpscan --url example.com -e u --passwords /path/to/password_file.txt` +#### The remote website is up, but does not seem to be running WordPress. + +If you get the `Scan Aborted: The remote website is up, but does not seem to be running WordPress.` error, it means that for some reason WPScan did not think that the site you are trying to scan is actually WordPress. If you think WPScan is wrong, you can supply the `--force` option to force WPScan to scan the site regardless. You may also need to set other options in this case, such as `--wp-content-dir` and `--wp-plugins-dir`. + ### Docker Cheat Sheet #### Pull the Docker repository