To prevent modifying the query string of a specific type of HTTP request, add the query string pattern to the $query_string_array array. After adding a new mode, test whether to block legitimate requests. Syntax examples are as follows:$ query_string_array = apply_filters( ‘query_string_items’, array( ‘PATTERN_1’, ‘PATTERN_2’, ‘PATTERN_3’);
Note: each pattern added must be declared between single quotation marks (\
The specific user agent of WordPress uses specific user agents such as viruses and malware robots that automatically block visitors to block visitors. Please add the user agent string in $user_agent_array. By limiting the maximum URL length of WordPress and limiting the number of characters available for configuring HTTP requests, WordPress installations can be protected from zero day attacks and other malicious attacks. \
Most malicious web application attacks use long URLs to exploit known vulnerabilities. Therefore, limiting the number of characters available in HTTP requests automatically protects the word press installation from such attacks. You can also block legitimate requests by limiting the number of characters used in the URL. Therefore, before enabling this security feature, please check the length of the longest URL in the WordPress installation (including the WordPress administration page (\/ WP admin \/) section). To activate and configure the maximum URL length, remove the comment handling (\
strlen( $_SERVER[‘REQUEST_URI’] ) > 255 ||
WordPress web application firewall test BBQ: block bad queries after the WordPress plug-in is installed, in order to verify whether it works, please request the following sample URL list to run multiple tests (replace some_site.com with domain). http:\/\/www.some_site.com\/..\/..\/..\/etc\/passwd http:\/\/www. some_site. com\/path\/? q=%00 http:\/\/www. some_site. If the COM \/ path \/ base64_ plug-in works normally, the server must respond with the HTTP status code 403forbidden when requesting these URLs. The above request is only a URL example and must be blocked by the BBQ: block bad requests plug-in. Multiple other tests can be run using the requests commonly used in actual hacking attacks.
BBQ test: if you are not sure what the server response is when sending the wrong query to Fiddler to block the malicious HTTP request of the plug-in, you can use Fiddler proxy to check the response. As highlighted in the screenshot below, in this test https:\/\/www.wpwhitesecurity.com\/contact\/base64_ If the URL is requested, you can verify whether the server responds with HTTP 403 Forbidden. Wrong query interception plug-in – WordPress web application firewall you have it! If you are looking for a highly customizable and powerful web application firewall for WordPress blogs and websites, please install and forget the BBQ: block bad query plug-in. BBQ: block bad queries from the WordPress plug-in repository or pro here
