Wordpress Pingback Locator - Metasploit
This page contains detailed information about how to use the auxiliary/scanner/http/wordpress_pingback_access metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Wordpress Pingback Locator
Module: auxiliary/scanner/http/wordpress_pingback_access
Source code: modules/auxiliary/scanner/http/wordpress_pingback_access.rb
Disclosure date: -
Last modification time: 2022-01-23 15:28:32 +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-2013-0235
This module will scan for wordpress sites with the Pingback API enabled. By interfacing with the API an attacker can cause the wordpress site to port scan an external target and return results. Refer to the wordpress_pingback_portscanner module. This issue was fixed in wordpress 3.5.1
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/scanner/http/wordpress_pingback_access
msf auxiliary(wordpress_pingback_access) > show options
... show and set options ...
msf auxiliary(wordpress_pingback_access) > set RHOSTS ip-range
msf auxiliary(wordpress_pingback_access) > exploit
Other examples of setting the RHOSTS option:
Example 1:
msf auxiliary(wordpress_pingback_access) > set RHOSTS 192.168.1.3-192.168.1.200
Example 2:
msf auxiliary(wordpress_pingback_access) > set RHOSTS 192.168.1.1/24
Example 3:
msf auxiliary(wordpress_pingback_access) > 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 scanner/http/wordpress_pingback_access auxiliary module looks in the msfconsole:
msf6 > use auxiliary/scanner/http/wordpress_pingback_access
msf6 auxiliary(scanner/http/wordpress_pingback_access) > show info
Name: Wordpress Pingback Locator
Module: auxiliary/scanner/http/wordpress_pingback_access
License: Metasploit Framework License (BSD)
Rank: Normal
Provided by:
Thomas McCarthy "smilingraccoon" <[email protected]>
Brandon McCann "zeknox" <[email protected]>
Christian Mehlmauer <[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)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The path to wordpress installation (e.g. /wordpress/)
THREADS 1 yes The number of concurrent threads (max one per host)
VHOST no HTTP server virtual host
Description:
This module will scan for wordpress sites with the Pingback API
enabled. By interfacing with the API an attacker can cause the
wordpress site to port scan an external target and return results.
Refer to the wordpress_pingback_portscanner module. This issue was
fixed in wordpress 3.5.1
References:
https://nvd.nist.gov/vuln/detail/CVE-2013-0235
http://www.securityfocus.com/archive/1/525045/30/30/threaded
http://www.ethicalhack3r.co.uk/security/introduction-to-the-wordpress-xml-rpc-api/
https://github.com/FireFart/WordpressPingbackPortScanner
Module Options
This is a complete list of options available in the scanner/http/wordpress_pingback_access auxiliary module:
msf6 auxiliary(scanner/http/wordpress_pingback_access) > show options
Module options (auxiliary/scanner/http/wordpress_pingback_access):
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 path to wordpress installation (e.g. /wordpress/)
THREADS 1 yes The number of concurrent threads (max one per host)
VHOST no HTTP server virtual host
Advanced Options
Here is a complete list of advanced options supported by the scanner/http/wordpress_pingback_access auxiliary module:
msf6 auxiliary(scanner/http/wordpress_pingback_access) > show advanced
Module advanced options (auxiliary/scanner/http/wordpress_pingback_access):
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
NUM_REDIRECTS 10 yes Number of HTTP redirects to follow
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 scanner/http/wordpress_pingback_access module can do:
msf6 auxiliary(scanner/http/wordpress_pingback_access) > show actions
Auxiliary actions:
Name Description
---- -----------
Evasion Options
Here is the full list of possible evasion options supported by the scanner/http/wordpress_pingback_access auxiliary module in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 auxiliary(scanner/http/wordpress_pingback_access) > 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.
<IP> - X-Pingback header not found
Here is a relevant code snippet related to the "<IP> - X-Pingback header not found" error message:
71: # Check if X-Pingback exists and return value
72: if res
73: if res['X-Pingback']
74: return res['X-Pingback']
75: else
76: vprint_status("#{ip} - X-Pingback header not found")
77: return nil
78: end
79: else
80: return nil
81: end
<IP> - Unable to connect
Here is a relevant code snippet related to the "<IP> - Unable to connect" error message:
78: end
79: else
80: return nil
81: end
82: rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
83: vprint_error("#{ip} - Unable to connect")
84: return nil
85: end
86: end
87:
88: # Creates the XML data to be sent
Unable to connect to <URI>
Here is a relevant code snippet related to the "Unable to connect to <URI>" error message:
129: 'uri' => "#{uri}",
130: 'method' => 'POST',
131: 'data' => "#{pingback_xml}"
132: })
133: rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
134: vprint_error("Unable to connect to #{uri}")
135: return nil
136: end
137: return res
138: end
139:
<IP> does not seeem to be Wordpress site
Here is a relevant code snippet related to the "<IP> does not seeem to be Wordpress site" error message:
150: end
151:
152: # main control method
153: def run_host(ip)
154: unless wordpress_and_online?
155: print_error("#{ip} does not seeem to be Wordpress site")
156: return
157: end
158:
159: # call method to get xmlrpc url
160: xmlrpc = get_xml_rpc_url(ip)
<IP> - It doesn't appear to be vulnerable
Here is a relevant code snippet related to the "<IP> - It doesn't appear to be vulnerable" error message:
159: # call method to get xmlrpc url
160: xmlrpc = get_xml_rpc_url(ip)
161:
162: # once xmlrpc url is found, get_blog_posts
163: if xmlrpc.nil?
164: print_error("#{ip} - It doesn't appear to be vulnerable")
165: else
166: hash = get_blog_posts(xmlrpc, ip)
167:
168: if hash
169: store_vuln(ip, hash) if @db_active
<IP> - X-Pingback enabled but no vulnerable blogs found
Here is a relevant code snippet related to the "<IP> - X-Pingback enabled but no vulnerable blogs found" error message:
165: else
166: hash = get_blog_posts(xmlrpc, ip)
167:
168: if hash
169: store_vuln(ip, hash) if @db_active
170: else
171: print_status("#{ip} - X-Pingback enabled but no vulnerable blogs found")
172: end
173: end
174: end
175: end
Go back to menu.
Related Pull Requests
- #10299 Merged Pull Request: Add 88 CVEs to various auxiliary and exploit modules
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #6089 Merged Pull Request: Fix HTTP mixins namespaces
- #3216 Merged Pull Request: Update @Meatballs1 and @FireFart in authors.rb
- #2525 Merged Pull Request: Change module boilerplate
- #2267 Merged Pull Request: Wordpress mixin
- #1524 Merged Pull Request: Update module description
- #1335 Merged Pull Request: Added Name and Emailadress
- #1249 Merged Pull Request: aux scanner for wordpress 3.5 sites with X-Pingback
References
- CVE-2013-0235
- http://www.securityfocus.com/archive/1/525045/30/30/threaded
- http://www.ethicalhack3r.co.uk/security/introduction-to-the-wordpress-xml-rpc-api/
- https://github.com/FireFart/WordpressPingbackPortScanner
See Also
Check also the following modules related to this module:
- auxiliary/scanner/http/wordpress_content_injection
- auxiliary/scanner/http/wordpress_cp_calendar_sqli
- auxiliary/scanner/http/wordpress_ghost_scanner
- auxiliary/scanner/http/wordpress_login_enum
- auxiliary/scanner/http/wordpress_multicall_creds
- auxiliary/scanner/http/wordpress_scanner
- auxiliary/scanner/http/wordpress_xmlrpc_login
- auxiliary/dos/http/wordpress_directory_traversal_dos
- auxiliary/dos/http/wordpress_long_password_dos
- auxiliary/dos/http/wordpress_xmlrpc_dos
- auxiliary/admin/http/axigen_file_access
- exploit/linux/http/vmware_workspace_one_access_cve_2022_22954
- exploit/linux/local/vmware_workspace_one_access_certproxy_lpe
- exploit/linux/snmp/net_snmpd_rw_access
- exploit/multi/browser/java_verifier_field_access
- exploit/unix/webapp/citrix_access_gateway_exec
- exploit/windows/http/ericom_access_now_bof
- auxiliary/scanner/http/advantech_webaccess_login
- auxiliary/scanner/http/atlassian_crowd_fileaccess
- auxiliary/scanner/http/hp_sitescope_getfileinternal_fileaccess
- auxiliary/scanner/http/hp_sitescope_loadfilecontent_fileaccess
- auxiliary/scanner/http/mediawiki_svg_fileaccess
- auxiliary/scanner/http/novell_file_reporter_fsfui_fileaccess
- auxiliary/scanner/http/novell_file_reporter_srs_fileaccess
- auxiliary/scanner/http/zenworks_assetmanagement_fileaccess
- auxiliary/scanner/misc/easycafe_server_fileaccess
- auxiliary/scanner/misc/zenworks_preboot_fileaccess
- auxiliary/scanner/sap/sap_mgmt_con_getaccesspoints
- auxiliary/scanner/scada/indusoft_ntwebserver_fileaccess
- auxiliary/scanner/scada/sielco_winlog_fileaccess
- auxiliary/admin/http/contentkeeper_fileaccess
- auxiliary/admin/scada/advantech_webaccess_dbvisitor_sqli
- auxiliary/admin/webmin/edit_html_fileaccess
- auxiliary/gather/advantech_webaccess_creds
Authors
- Thomas McCarthy "smilingraccoon" <smilingraccoon[at]gmail.com>
- Brandon McCann "zeknox" <bmccann[at]accuvant.com>
- Christian Mehlmauer
Version
This page has been produced using Metasploit Framework version 6.2.23-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.