Description
By manipulating the HTTP verb it was possible to bypass the authorization on this directory. The scanner sent a request with POST HTTP verb and managed to bypass the authorization. An application is vulnerable to HTTP Verb tampering if the following conditions hold:
- it uses a security control that lists HTTP verbs
- the security control fails to block verbs that are not listed
- it has GET functionality that is not idempotent or will execute with an arbitrary HTTP verb
For example, Apache with .htaccess is vulnerable if HTTP verbs are specified using the LIMIT keyword:
<Limit GET> require valid-user </Limit>
Remediation
In the case of Apache + .htaccess, don't use HTTP verb restrictions or use LimitExcept.
Check references for more information on how to fix this problem on other platforms.
References
Related Vulnerabilities
WordPress Plugin Authorize.net Payment Gateway For WooCommerce Security Bypass (2.0)
WordPress Plugin WC Duplicate Order Security Bypass (1.5)
WordPress Plugin YITH WooCommerce Brands Add-On Security Bypass (1.3.6)
WordPress Plugin Site Offline Or Coming Soon Or Maintenance Mode Security Bypass (1.5.2)
WordPress Plugin WP Affiliate Disclosure Security Bypass (1.1.3)