Updated WPScan User Documentation (markdown)
@@ -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`
|
`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
|
### Docker Cheat Sheet
|
||||||
|
|
||||||
#### Pull the Docker repository
|
#### Pull the Docker repository
|
||||||
|
|||||||
Reference in New Issue
Block a user