Replies: 0
Hi,
I noticed that when Wordfence block XSS or Directory Travelsal attacks, it doesnt put the source IP in black list right after the first attack. So I have reports like the following, as you see all attacks came from the same IP, so why it was not blacklisted and allowed it to score 135 attacks?
Increased Attack Rate: The Wordfence Web Application Firewall has blocked <strong>135 attacks over the last 10 minutes</strong>. Below is a sample of these recent attacks: 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: arquivo=../../../../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: file=../../../../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: files=../../../../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: file=../../../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: f=../../../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: url=../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: target=../../../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: filename=../../../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: file=../../../wp-config.php 11 Febbraio, 2020 1:19pm - 194.60.254.243 (Ukraine) - Blocked for Directory Traversal - wp-config.php in query string: page=../../../../wp-config.php