Updated WPScan User Documentation (markdown)
@@ -57,7 +57,9 @@ _Get your API token from [wpvulndb.com](https://wpvulndb.com/) if you also want
|
|||||||
|
|
||||||
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://wpvulndb.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. A free API token is available, as well as paid plans, depending on your usage needs.
|
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.
|
||||||
|
|
||||||
|
A free API token is available, as well as paid plans, depending on your usage needs.
|
||||||
|
|
||||||
If you do not supply an API token, WPScan will work as normal, with the exception that when a WordPress version, plugin or theme is detected, the associated known vulnerabilities will not be displayed.
|
If you do not supply an API token, WPScan will work as normal, with the exception that when a WordPress version, plugin or theme is detected, the associated known vulnerabilities will not be displayed.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user