garfield/wpscan
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update domain

Ryan Dewhurst
2020-10-20 11:59:14 +02:00
parent 5a432ead28
commit 32a2f273f1
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
WPScan-User-Documentation.md

@@ -108,7 +108,7 @@ If no option is supplied to the `-e` flag, then the default will be: `vp,vt,tt,c
Here we have put together a bunch of common commands that will help you get started quickly.
_NOTE: Get your API token from [wpvulndb.com](https://wpvulndb.com/) if you also want the vulnerabilities associated with the detected plugin displaying._
_NOTE: Get your API token from [wpscan.com](https://wpscan.com/) if you also want the vulnerabilities associated with the detected plugin displaying._
- For all plugins with known vulnerabilities:
@@ -143,7 +143,7 @@ The `wpscan-output.txt` file now exists on the host machine at `~/docker-bind/wp
## Vulnerability Database
WPScan uses the [WordPress Vulnerability Database](https://wpvulndb.com/api) API in real time to retrieve known vulnerabilities that affect WordPress core, plugins and themes.
WPScan uses the [WordPress Vulnerability Database](https://wpscan.com/api) API in real time to retrieve known vulnerabilities that affect WordPress core, plugins and themes.
For the vulnerability information to be shown within WPScan you will need to supply an API token with the `--api-token YOUR_TOKEN` option. Alternatively, you can supply the API token from a WPScan configuration file.
@@ -161,6 +161,6 @@ If WPScan is not working as expected, you can use the `--proxy` option, and use
## Keeping Informed
We blog here - [https://blog.wpscan.org/](https://blog.wpscan.org/)
We blog here - [https://blog.wpscan.com/](https://blog.wpscan.com/)
We tweet here - [https://twitter.com/\_wpscan\_](https://twitter.com/\_wpscan\_)