From cb9701eaeffffbb8b27fc9a5fa1d2cbdb211d4cb Mon Sep 17 00:00:00 2001 From: Miguel Xavier Penha Neto Date: Sun, 28 May 2023 00:25:01 -0300 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 35fce0fe..8aebac38 100644 --- a/README.md +++ b/README.md @@ -90,7 +90,7 @@ The DB is located at ~/.wpscan/db The WPScan CLI tool uses the [WordPress Vulnerability Database API](https://wpscan.com/api) to retrieve WordPress vulnerability data in real time. For WPScan to retrieve the vulnerability data an API token must be supplied via the `--api-token` option, or via a configuration file, as discussed below. An API token can be obtained by registering an account on [WPScan.com](https://wpscan.com/register). -Up to **75** API requests per day are given free of charge, that should be suitable to scan most WordPress websites at least once per day. When the daily 75 API requests are exhausted, WPScan will continue to work as normal but without any vulnerability data. +Up to **25** API requests per day are given free of charge, that should be suitable to scan most WordPress websites at least once per day. When the daily 25 API requests are exhausted, WPScan will continue to work as normal but without any vulnerability data. ### How many API requests do you need?