From 420c83770e459307b35ef1233b2accfff8536be2 Mon Sep 17 00:00:00 2001 From: Ryan Dewhurst Date: Fri, 3 Apr 2020 09:57:32 +0200 Subject: [PATCH] Updated WPScan User Documentation (markdown) --- WPScan-User-Documentation.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/WPScan-User-Documentation.md b/WPScan-User-Documentation.md index 9b636e1..c484602 100644 --- a/WPScan-User-Documentation.md +++ b/WPScan-User-Documentation.md @@ -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. -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.